It's great that SPM added support for bundles!
I went ahead and added SPM support for a library that I'm working on which includes several .xib files and also an en.lproj. This worked well - running both in the simulator and on device. So far so good.
Next, I had a look if it's possible to already use this in a TestFlight build. Unfortunately that failed as App Store Connect responded with: ERROR ITMS-90535: "Unexpected CFBundleExectuable Key" ... consider removing the CFBundleExectuable key from its Info.plist and using a CFBundlePackageType of BNDL. Inspecting the built products, I can indeed see that build product of my app contains .bundle for my library (as expected) and digging into that I can confirm that it has a CFBundleExecutable with the same name as the bundle file (without file extension) and that CFBundlePackageType is already set to BNDL.
I wonder how to resolve this. Did I miss a step along the way, is this an issue with SPM or is App Store Connect just not ready for this yet?
I went ahead and added SPM support for a library that I'm working on which includes several .xib files and also an en.lproj. This worked well - running both in the simulator and on device. So far so good.
Next, I had a look if it's possible to already use this in a TestFlight build. Unfortunately that failed as App Store Connect responded with: ERROR ITMS-90535: "Unexpected CFBundleExectuable Key" ... consider removing the CFBundleExectuable key from its Info.plist and using a CFBundlePackageType of BNDL. Inspecting the built products, I can indeed see that build product of my app contains .bundle for my library (as expected) and digging into that I can confirm that it has a CFBundleExecutable with the same name as the bundle file (without file extension) and that CFBundlePackageType is already set to BNDL.
I wonder how to resolve this. Did I miss a step along the way, is this an issue with SPM or is App Store Connect just not ready for this yet?
That's a known issue:
> Apps that use Swift packages containing resources are not successfully imported. As a workaround, manually remove the CFBundleExecutable keys from the Info.plist files of the embedded resource bundles.
> Apps that use Swift packages containing resources are not successfully imported. As a workaround, manually remove the CFBundleExecutable keys from the Info.plist files of the embedded resource bundles.