ios – Sudden CFBundleExecutable Key – cannot discover the correct CFBundleExecutable in plist.information to delete

0
121


Like many others, I am experiencing a Sudden CFBundleExecutable Key error when making an attempt to add my app to TestFlight by way of Xcode. Sadly, I’ve tried lots of the issues urged up to now, and have not discovered an answer.

As is, I can construct my undertaking domestically, however as quickly as I Challenge –> Archive and construct my app there, and I click on Distribute, I get the next errors:

Sudden CFBundleExecutable Key. The bundle at 'Payload/wanderly.app/Frameworks/Lottie.framework/LottiePrivacyInfo.bundle' doesn't include a bundle executable. If this bundle deliberately doesn't include an executable, take into account eradicating the CFBundleExecutable key from its Information.plist and utilizing a CFBundlePackageType of BNDL. If this bundle is a part of a third-party framework, take into account contacting the developer of the framework for an replace to deal with this subject.

If I delete Lottie from my undertaking, I nonetheless get an identical subject:

Sudden CFBundleExecutable Key. The bundle at 'Payload/wanderly.app/Frameworks/React.framework/AccessibilityResources.bundle' doesn't include a bundle executable. If this bundle deliberately doesn't include an executable, take into account eradicating the CFBundleExecutable key from its Information.plist and utilizing a CFBundlePackageType of BNDL. If this bundle is a part of a third-party framework, take into account contacting the developer of the framework for an replace to deal with this subject.

Which is bizarre, since lots of the studies of this error are about libraries, however that is associated to core React/ReactNative (it is a ReactNative app).

I’ve tried a wide range of various things up to now:

  1. Utterly cleansing my undertaking (delete pods, node_modules, and so forth) + Clear Construct Folder, and no cube.

  2. As some options have talked about, I’ve additionally checked out Copy Bundle Assets, and there is no inaccurate information. I’ve additionally set ENABLE_BITCODE to NO.

No weird additions to Copy Bundle Resources

  1. As most options have talked about, I’ve tried going to the information.plist for every package deal to attempt to take away the CFBundleExecutable key, however have been unable to seek out reference to the talked about executable OR it would not appear to work if I take away it. That is maybe essentially the most ambiguous / difficult side, since there are various locations the place the .plist will be discovered, and different solutions do not appear to attach the dots sufficient for me.

3a) If I do a Cmd + Shift + O for information.plist in Xcode, I get an inventory of information, however none of them precisely match the bundles listed in my errors.

if I search for info.plist in XCode

info.plist for one lottie entry

info.plist for the other one

You will additionally discover that these all have the Bundle OS Kind Code already set to BNDL, and there is not point out of the CFBundleExecutable key / Executable Identify.

3b) I’ve additionally regarded instantly into the created “Archive”, for an archive, I proper click on to “Present in Finder”, after which proper clicked on the .xcarchive to “Present Bundle Contents” –> dSYMs –> Lottie.framework.dSYM –> “Present Bundle Contents” –> Contents –> Information.plist, and that does not include something like what I am in search of:

directly looking into the contents of a built archive

3c) I’ve additionally regarded into Pods instantly in XCode, and checked out associated Targets. Within the settings it’s going to present a “Information.plist File” location like /project_root/ios/Pods/Goal Assist Information/lottie-ios/ResourceBundle-LottiePrivacyInfo-lottie-ios-Information.plist. Openning that file would not present a CFBundleExecutable / Executable Identify key:

looking for info.plist under Target Support Files

3d) I’ve additionally tried looking my undertaking below Pods for mentions of CFBundleExecutable, and received the next output:

MacBook-Professional-2 ios % grep -r "CFBundleExecutable" Pods/**/*.plist

Pods/Goal Assist Information/Pods-wanderly-wanderlyTests/Pods-wanderly-wanderlyTests-Information.plist:  <key>CFBundleExecutable</key>
Pods/Goal Assist Information/Pods-wanderly/Pods-wanderly-Information.plist:  <key>CFBundleExecutable</key>
Pods/hermes-engine/destroot/Library/Frameworks/macosx/hermes.framework/Variations/0/Assets/Information.plist: <key>CFBundleExecutable</key>
Pods/hermes-engine/destroot/Library/Frameworks/common/hermes.xcframework/ios-arm64/hermes.framework/Information.plist:  <key>CFBundleExecutable</key>
Pods/hermes-engine/destroot/Library/Frameworks/common/hermes.xcframework/ios-arm64_x86_64-maccatalyst/hermes.framework/Variations/0/Assets/Information.plist:  <key>CFBundleExecutable</key>
Pods/hermes-engine/destroot/Library/Frameworks/common/hermes.xcframework/ios-arm64_x86_64-simulator/hermes.framework/Information.plist: <key>CFBundleExecutable</key>

which does not point out any of the named bundles talked about within the error.

3e) I’ve additionally regarded up wanderly.app in Finder. If I proper click on and received to “Present Bundle Contents”, I get to a listing the place I really see the packages within the error. If I open the information.plist for every, I really see the keys and the problem the place it contains CFBundleExecutable key and the CFBundlePackageType, and I can delete / edit these information (delete CFBundleExectable and including BNDL). However after I change them, nothing adjustments… I believe as a result of this listing is said to my domestically working construct, not the archive that I am making an attempt to add.

the info.plists in wanderly.app Show Package Contents

the right keys to be deleting

I am essentially the most optimistic about this final technique, however I am lacking the hyperlink to find out how to get these adjustments to be a part of what construct I am making an attempt to add to TestFlight.

Can anybody assist me join the dots right here? I would actually recognize it.