Unexpected CFBundleExecutable key

Question

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:

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 1

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.

Answer 2

Encountered this with AviarySDK on Xcode 7 GM, while submitting to the App Store.

First I'd check to see whether you're on the latest version of your library - the vendor may have fixed this already. If you are still facing this problem however, as Sleiman describes you need to remove the CFBundleExecutable key from the plist file for the offending library.

Cmd + Shift + O and type "Info.plist", you can then find the appropriate file:

Once editing the plist, you may be seeing descriptive names (instead of the CFBundleExecutable and other keys. I couldn't edit this file in an external editor, so I had to switch to view raw keys/values by right-clicking on the list:

You can now see the CFBundleExecutable key (which has a description of "Executable file") which you can delete.

For AviarySDK I did this twice, once for each Info.plist seen in the above image, and was then able to successfully submit.

Answer 3

I solve this problem as follows: We have to remove all the "Executable files" of the following packages:

• GooglePlus.bundle
• GPPCommonSharedResources.bundle
• GPPShareboxSharedResources.bundle

Be sure that "Bundle type code" is equal BNDL

Important: Do not edit anything in the info.plist the main project.

Attached screens as they should be his "info.plist" listed above each package.

Answer 4

Here's what worked for me

1. Apple-Shift-F, search for CFBundleExecutable
2. Click each one except "PODS" or your main target
3. Delete it (delete key)

Answer 5

If the build is submitted through Less than(<) Xcode 7.0 then it will be submitted and also I have solved it by following way for Xcode 7:

Searched for info.plist in the projects Project Navigator as like following image:

Now opened these info.plist files one by one and deleted the BundleExecutable key EXCEPT the target's info.plist

Now cleaned the project and achieved and It is submitted with No issue.

Answer 6

I had the same issue in Google Maps Library i removed CFBundleExecutable key inside GMSCoreResources.bundle (Info.plist) which is SDK's info.plist clean project and upload to appstore.

Happy Programming.

Answer 7

Just check your Build Settings => Enable Bitcode, and set it NO

Answer 8

In my case I just Drag and Drop The SDK In folder include info.plist file which is not in use. That's create the issue for me. So find the unused info.plist file and delete it from the Source code.

Answer 9

One additional note: sometimes if you have additional targets there will be target properties that may also include the key (in the "Info" section), so make sure to check those and remove it from there also. I discovered this with one of the bundles I was trying to include. I deleted the info from the plist, but kept getting the error.

Answer 10

If you're seeing this error from a library installed via CocoaPods, try a pod update <OFFENDING POD NAME>

That solved the problem for me.

Answer 11

I just added word "BNDL" to appropriate place in plist "Bundle creator OS Type code".

Answer 12

a simple answer to this is just disable CODE_SIGNING_ALLOWED in the Podfile. and all working fine.

here is the code

post_install do |installer|
    react_native_post_install(installer)
    
    
    #############
      installer.pods_project.targets.each do |target|
            
        ### Added for Maps
        if target.name == 'RCT-Folly'
          target.build_configurations.each do |config|
            config.build_settings['HEADER_SEARCH_PATHS'] = "$(inherited) ${PODS_ROOT}/fmt/include"
            config.build_settings['CODE_SIGNING_ALLOWED'] = 'NO'
          end
        end
        #### Added For Maps Ended 

        if target.respond_to?(:product_type) and target.product_type == "com.apple.product-type.bundle"
          target.build_configurations.each do |config|
              config.build_settings['CODE_SIGNING_ALLOWED'] = 'NO'
              config.build_settings["DEVELOPMENT_TEAM"] = "XXXW7BNX6K" 
          end
        end
      end
    ############


    installer.pods_project.build_configurations.each do |config|
      config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64"
      config.build_settings['CODE_SIGNING_ALLOWED'] = 'NO'
      config.build_settings["ONLY_ACTIVE_ARCH"] = "YES"
    end
    #__apply_Xcode_12_5_M1_post_install_workaround(installer)
  
  end
end