Unexpected CFBundleExecutable key

Dumoko picture Dumoko · Aug 19, 2015 · Viewed 40.5k times · Source

After spending some time googling, something tells me that the issue is new.

We had a fully functional project supporting iOS7-8. Of course it was multiple times successfully submitted to AppStore.

We use pods, lots of tracking and monitoring, like GA and Instabug.

Now we decided to submit a version of the app built on Xcode 7 on iOS 9 to TestFlight.

We disabled bitcode, since many pods, like Flurry and other prebuilt libraries does not include it.

The build was successful, after the submission to iTunesConnect we get this: enter image description here

We had same for GoogleAppIndexing library (in pods too), but we removed it, just to make it work. Now - Instabug. It is going too far, so I am trying to understand what is going on in iOS 9 and what are the changes that made a fully working project to start throwing such errors.

Any thoughts and ideas are welcomed! Please share your experience, and if I missed something, I will gladly share my steps.

Answer

Sleiman picture Sleiman · Aug 20, 2015

I encountered the same problem today with the same exact error message when trying to submit our app (using Xcode 7 beta 5) but instead of the instabug.bundle bit, it was for me TencentOpenApi_IOS_Bundle.bundle.

I solved the problem by finding the named bundle in the project then - just as the error message suggests - edited the Info.plist that is in the bundle by removing the CFBundleExecutable key. The CFBundlePackageType key was already set to BNDL so I didn't touch it.

After these changes I did Product > Clean and then had no problem submitting the app to the App store.

I hope this helps.