ERROR ITMS-90075 submitting to iTunes with FB & Air 28 using dynamic frameworks
We are having trouble uploading our Air app to the ios appstore with the the new external framework code sigining in Air 28 with FB with the following error: "ERROR ITMS-90075: "This bundle is invalid. The application-identifier entitlement is missing; it should contain your 10-character Apple Developer ID, followed by a dot, followed by your bundle identifier."
Usually, this is due to using the wrong provisioning profile or not having the correct bundle id or app id in app.xml match the provisioning profile. But not in this case.
Before this, we were using Air 25, and using a script to "re-sign" the external frameworks and .app before submitting to Apple, and that was working fine. We also tried the resigning script with Air 28 but that didn't solve the problem.
In terms of troubleshooting:
1. if we simply uncheck the "Frameworks" folder (containing the external frameworks and swift dylibs) in the packaging settings for the release build, the app is accepted by itunesconnect. If we include the "Frameworks" folder in the packaging, no dice, we get the ERROR ITMS-90075 error shown above.
2. suspecting this has something to do with code signing and entitlements with FB, we used Xcode to resign and upload to the appstore, and were successful doing it this way:
- created a dummy app in Xcode and archived it
- opened the xcode archive and replaced the dummy .app with the .app from the release build made by FB and updated the info.plist in the archive folder.
- deleted the _Codesign in .app and deleted the embedded frameworks in the "Frameworks" folder and replaced those with unsigned copies.
- copied the SwiftSupport folder from the FB .app to the copy now in the Xcode archive folder.
- used xcode to resign the app and frameworks and upload to the appstore. - Success!
3. Comparing the re-signed .app using xcode to the original from FB, the main difference seems to the that FB is applying entitlements with the code signing, and Xcode is not.
Anyway, we finally were able to upload the app store, but it required a convoluted messy procedure above using xcode to do it. Again, this seems like a problem with the way FB is packaging/signing the app, but not certain.
