I have received an mail from Apple that my app has been rejected.
The reason is:
We have discovered one or more issues with your recent delivery for
“Secure Send”. To process your delivery, the following issues must be
corrected:Invalid Code Signing Entitlements – Your application bundle’s
signature contains code signing entitlements that are not supported.
Please check your Xcode project’s code signing entitlements
configuration, and remove any unneeded entitlements.Specifically, key “com.apple.developer.default-data-protection” is not
supported.Once these issues have been corrected, go to the Version Details page
and click “Ready to Upload Binary.” Continue through the submission
process until the app status is “Waiting for Upload.” You can then
deliver the corrected binary.
I have found this question where the exactly same issue appears. The marked solution is to disable data protection in the provisioning profile. But when I do this my app cannot store the files securely using data protection, what it definitely should do!
I have also tried to disable Data Protection but then all files are stored in DataProtectionClassNone regardless which protection class is set.
Thanks in advance!
Okay, it is definitely not deprecated! It will be introduced with iOS6 and I had these settings because of my iOS6 Beta. That’s the reason why our binary was invalid.
Our deployment target was set to iOS5 but this configuration key will be introduced with iOS6. So the automatic binary check failed because it didn’t know this flag for iOS5 apps.
More on this: