-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App Store Connect Operation Error when using SPM integration #317
Comments
This seems to be a SPM issue related to binary frameworks in general: https://forums.swift.org/t/swift-package-binary-framework-issue/41922 |
I can confirm that the workaround as described in the Swift Forums fixes the issue. This is the script I am using as the last "Run Script" in the build phase of the main app:
Input Files: |
@mbuchetics Thank you for posting this! |
We added a note about this issue and the workaround in the SPM section of the README. |
Integration Details (please complete the following information):
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:
When looking into the produced
.app
I can see thatCardinalMobile.framework
andPPRiskMagnes.framework
both exist twice: in theFrameworks
folder AND in thePlugIns
folder.This only happens if the app that is being archived contains extensions, in my case an
Intent
andIntentUI
app extension .To Reproduce
Steps to reproduce the behavior:
9.0.0-beta1
(I haven't tested with the master branch)Intent
extension (which also adds anIntentUI
extension).app
Expected behavior
No
.framework
files copied into thePlugIns
folder. App Store Connect upload to run without errors.Screenshots
The text was updated successfully, but these errors were encountered: