Description
Integration Details (please complete the following information):
- SDK/Library Version: 9.0.0-beta1
- Environment: Sandbox
- iOS Version: unrelated
- Device: unrelated
- Integration type & version: Xcode 12.4 with SPM
Describe the bug
I integrated v9.0.0-beta1 of the Drop In SDK using SPM (previously using Carthage). Building & running the app works fine. However, when trying to upload a build to App Store Connect, it fails with the following errors:
App Store Connect Operation Error
Invalid directory. The bundle Payload/Fahrgast.app/PlugIns/CardinalMobile.framework is not contained in a correctly named directory. It should be under "Frameworks".
App Store Connect Operation Error
Invalid directory. The bundle Payload/Fahrgast.app/PlugIns/PPRiskMagnes.framework is not contained in a correctly named directory. It should be under "Frameworks".
App Store Connect Operation Error
CFBundleIdentifier Collision. There is more than one bundle with the CFBundleIdentifier value 'com.cardinalcommerce.CardinalMobile' under the iOS application 'Fahrgast.app'.
App Store Connect Operation Error
CFBundleIdentifier Collision. There is more than one bundle with the CFBundleIdentifier value 'com.paypal.PPRiskMagnes' under the iOS application 'Fahrgast.app'.
When looking into the produced .app
I can see that CardinalMobile.framework
and PPRiskMagnes.framework
both exist twice: in the Frameworks
folder AND in the PlugIns
folder.
This only happens if the app that is being archived contains extensions, in my case an Intent
and IntentUI
app extension .
To Reproduce
Steps to reproduce the behavior:
- Open the SPMTest project
- Change the SPM dependency to use version
9.0.0-beta1
(I haven't tested with the master branch) - Add an
Intent
extension (which also adds anIntentUI
extension) - Archive the project
- Inspect the produced
.app
Expected behavior
No .framework
files copied into the PlugIns
folder. App Store Connect upload to run without errors.