Getting error when Adding app in App store - ios

'/Payload/Runner.app/Frameworks/App.framework/flutter_assets/ios/Runner/Info.plist' does not contain a bundle executable. If this bundle intentionally does not contain an executable, consider removing the CFBundleExecutable key from its Info.plist and using a CFBundlePackageType of BNDL. If this bundle is part of a third-party
If you have any idea please tell me
Thanks

Update flutter version, this issue was fixed in version 1.2

Related

ITMS-90535: Unexpected CFBundleExecutable Key

ITMS-90535: Unexpected CFBundleExecutable Key - The bundle at
'/Payload/Runner.app/Frameworks/App.framework/flutter_assets/ios/Runner/Info.plist'
does not contain a bundle executable. If this bundle intentionally
does not contain an executable, consider removing the
CFBundleExecutable key from its Info.plist and using a
CFBundlePackageType of BNDL. If this bundle is part of a third-party
framework, consider contacting the developer of the framework for an
update to address this issue.
How to resolve this issue? I searched my entire project, I couldn't find this path anywhere In the project, and all the missing CFBundleExecutables CFBundlePackageTypes is in BNDL
Please check Info.plist added to Copy Bundle Resources in Build Phase. If so just remove it from Copy Bundle Resources.

App store submission error Invalid Bundle Structure

I am receiving the following error from XCode 8.1 when trying to submit a previously successful submitted app version upgrade:
ERROR ITMS-90171: "Invalid Bundle Structure - The binary file 'Particle.app/Particle_armv7' is not permitted. Your app can’t contain standalone executables or libraries, other than the CFBundleExecutable of supported bundles. Refer to the Bundle Programming Guide at https://developer.apple.com/go/?id=bundle-structure for information on the iOS app bundle structure."
ERROR ITMS-90171: "Invalid Bundle Structure - The binary file 'Particle.app/Particle_armv7' is not permitted. Your app can’t contain standalone executables or libraries, other than the CFBundleExecutable of supported bundles. Refer to the Bundle Programming Guide at https://developer.apple.com/go/?id=bundle-structure for information on the iOS app bundle structure."
I did not modify anything in regards to architectures this build.
Any idea where I should look to solve this problem?
This error occurs when a static library file is mistakenly copied into the app bundle.
You should link the libYourLibrary.a static library via a Link Binary with Libraries build phase.
It should NOT be added to the target's Copy Bundle Resources build phase.
Ok, the problem was that there was an extra build variant specified as "armv7" in the build settings. No idea why. Reverting to "normal" only fixed this issue.
from project.pbxproj:
buildSettings = {
ASSETCATALOG_COMPILER_APPICON_NAME = AppIcon;
ASSETCATALOG_COMPILER_LAUNCHIMAGE_NAME = LaunchImage;
- BUILD_VARIANTS = (
- armv7,
- normal,
- );
+ BUILD_VARIANTS = normal;
removed lines marked with - added lines with +
Issue - two binaries were included in bundle:
Fix - make sure only "normal" is under Build variants:

App Processing Error: Unexpected CFBundleExecutable Key

I am trying to submit to Apple with bitCode enabled. Everytime i submit I am getting this email.
We have discovered one or more issues with your recent delivery for "MyAPPP". To process your delivery, the following issues must be corrected:
Unexpected CFBundleExecutable Key - The bundle at '/Payload/MyAPPP.app/Base.lproj' does not contain a bundle executable. If this bundle intentionally does not contain an executable, consider removing the CFBundleExecutable key from its Info.plist and using a CFBundlePackageType of BNDL. If this bundle is part of a third-party framework, consider contacting the developer of the framework for an update to address this issue.
Once these issues have been corrected, you can then redeliver the corrected binary.
My application's info.plist has following.
Cocoa Pods for every pod has info.plist as
All Pods are here.
I faced the same issue. Finally I got a solution.
In my case, Info.plist file was added to Copy Bundle Resources in Build Phase. I just remove it from Copy Bundle Resources and it worked!

iOS, GoogleMaps, Unexpected CFBundleExecutable Key

I am trying to upload archive for TestFlight testing in Xcode 7 and it gives me the error:
I tried to remove CFBundleExecutable key and set CFBundlePackageType to BNDL, the way it is recommended here:
Unexpected CFBundleExecutable key
and here:
https://code.google.com/p/gmaps-api-issues/issues/detail?id=8488
However, it starts giving me the following error:
My version of google maps is 1.11.0
So, I am not sure what to try next. Any suggestions?
The solution was to reinstall Google Maps from version 1.11.0 to 1.11.1. No info.plist key changes/deletions were necessary. In the process I also faced the pod install command taking forever to run and used the appropriate solution:
cocoapods - 'pod install' takes forever
CFBundleSupportedPlatforms Replace with iPhoneSimulator to iPhoneOS in both
GoogleMap.info -> info.plist and GSMCoreResources.bundle -> info.plist
Also remove Executable file property in GoogleMap.bundle -> info.plist and GSMCoreResources.bundle -> info.plist

ERROR ITMS-90207 Invalid bundle

I’m having issue when uploading to app store an app with this framework.
ERROR ITMS-90207 "Invalid bundle. The bundle at .../TesseractOCR.framework' does not contain a bundle executable.
In my Xcodeproj i have another project inside, i'm including the framework on dependencies, linked libraries and Copy Files.
Do you know something about this issue?.
Many Thanks, Nahuel.
I was having the same problem. I fixed the issue by following this process:
In your info.plist file, under the key Executable file, add the value $(EXECUTABLE_NAME).
I solved this by changing Mach-O Type to Dynamic Library in Build Settings.
Xcode wasn't generating an executable.
I solved it by setting Bitcode off. (below two are related settings)
Build Settings > Build Options > Enable Bitcode : NO
Uncheck "Include Bitcode" when uploading app to Itunes Connect (after archiving)

Resources