Skip to content
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

Archive Validation Error: The bundle at AWSMobileClient.framework contains disallowed file 'Frameworks'. #1123

Closed
cornr opened this issue Nov 26, 2018 · 4 comments
Assignees
Labels
bug Something isn't working investigating This issue is being investigated mobile client Issues related to AWSMobileClient

Comments

@cornr
Copy link
Contributor

cornr commented Nov 26, 2018

Describe the bug
After updating from 2.6.18 to 2.7.3 we get following error when deploying to the app store.

Invalid Bundle. The bundle at 'My.app/Frameworks/AWSMobileClient.framework' contains disallowed file 'Frameworks'.

To Reproduce

  1. Use Carthage Setup as described in https://aws-amplify.github.io/docs/ios/manualsetup#carthage-setup (with carthage command: carthage update --platform ios --cache-builds --no-use-binaries)
  2. Upload to AppStore

Which AWS service(s) are affected?
AWSiOSSDKv2 2.7.x

Expected behavior
No Error from Appstore 😀
"AWSMobileClient.framework should not contain Frameworks directory."?

Additional context
I think this error results in embedding Swift Frameworks into AWSMobileClient.framework (since Swift code was introduced in 2.7). I wonder if this is necessary. Or do we have a project configuration error?

@lexmakali lexmakali added the mobile client Issues related to AWSMobileClient label Nov 26, 2018
@palpatim palpatim self-assigned this Nov 27, 2018
@palpatim palpatim added the investigating This issue is being investigated label Nov 27, 2018
@palpatim
Copy link
Member

It looks like we are setting the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES flag in the AWSMobileClient project. I'm testing to make sure our samples work as expected when we unset that, but I think that will be the fix.

@palpatim palpatim added the work in progress Issues was triaged and investigation done label Nov 27, 2018
@gokeji
Copy link

gokeji commented Dec 5, 2018

I've been experiencing the same issue. Setting ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES to false in the AWSMobileClient project allowed me to upload my binary to the App Store, and works as expected.

@rohandubal
Copy link
Contributor

Thanks for confirming @gokeji

We are working on a fix and it will be fixed in a future release.

Thanks,
Rohan

@rohandubal
Copy link
Contributor

Hello,

This issue is resolved in 2.7.4 SDK release. Please let us know if you continue to face issues.

Thanks,
Rohan

@rohandubal rohandubal assigned rohandubal and palpatim and unassigned palpatim and rohandubal Dec 7, 2018
@rohandubal rohandubal removed the work in progress Issues was triaged and investigation done label Dec 7, 2018
@frankmuellr frankmuellr added the bug Something isn't working label Jan 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working investigating This issue is being investigated mobile client Issues related to AWSMobileClient
Projects
None yet
Development

No branches or pull requests

6 participants