Email error: "Unexpected CFBundleExecutable key"

I have a problem that I was unable to resolve when submitting my app to the App Store . Application Deployment Target - iOS 10.0

I am getting this error with many third party libraries, I am using CocoaPods to manage libraries, and the error report is sent by email immediately after uploading to the App Store:

Unexpected key CFBundleExecutable - package in '/Payload/APP_NAME.app/Target Support files / FRAMEWORK _FOLDER / Info.plist' does not contain a batch executable. If this bundle intentionally does not contain an executable, consider removing the CFBundleExecutable key from its Info.plist and using the CFBundlePackageType for BNDL. If this package is part of a third party framework, consider contacting the framework developer for an update to resolve this issue

So I tried to remove the CFBundleExecutable key and use BNDL in the CFBundlePackageType key as the error shows and also because this is what I found on many forums. But while doing this, I cannot start the application with Xcode, the build is successful, but it asks for this message before opening it:

Binding on path /PATH/Payload/NAME.app/Frameworks/FRAMEWORK_NAME.framework missing or invalid CFBundleExecutable in Info.plist

And the app won't start.

So if I try to resolve the error, the application stops working with Xcode. I have not found any other solution and I need to upload my app to the App Store, btw this is the first time I upload it. I also tried looking to see if something related to CocoaPods but couldn't find anything. Also, I tried to install Enable bitcode : NO

but didn't work):

Any thoughts?

Hooray!

+3


source to share


2 answers


I found a solution:

Make sure that neither your target Info.plist file nor any of the folders or files created by CocoaPods are added to the Copy Bundle Resources in the Build Phases of your target application.



In my case the "Target Support Files" folder was added, so all the Info.plist files are libraries. Removing this fixed the problem and I can submit the app at last!

0


source


I found an answer on Git, this solved my problem. Just submitted my app and finished processing, hope this helps someone.

Found a solution:



The Support Target Files folder generated by CocoaPods has been added to the Copy Bundle Resources in the Build Phases of the application, so all Info.plist files are libraries. Removing this fixed the problem and I can submit the app at last!

0


source







All Articles