Aws-sdk-ios: Cannot distribute app because AWSCognito not built with full bitcode

Created on 17 Apr 2018  路  5Comments  路  Source: aws-amplify/aws-sdk-ios

  • What service are you using?

    • AWSDynamoDB
    • AWSMobileAnalytics
    • AWSCognito
    • AWSCore
    • AWSS3
  • In what version of SDK are you facing the problem?

2.6.16 (latest)

  • Is the issue limited to Simulators / Actual Devices?

The issue occurs when attempting to archive the app for distribution.

  • Can your problem be resolved if you bump to a higher version of SDK?

Currently using latest version.

  • Is this problem related to specific iOS version?

No, since this is archiving rather than building for a specific device/version.

  • How are you consuming the SDK? CocoaPods / Carthage / Prebuilt frameworks?

Prebuilt framework downloaded from https://aws.amazon.com/mobile/resources/

  • Can you give us steps to reproduce with a minimal, complete, and verifiable example? Please include any specific network conditions that might be required to reproduce the problem.

Archive an iMessage app with bitcode enabled, using the above mentioned frameworks.

ld: bitcode bundle could not be generated because '../lib/Amazon/aws-ios-sdk-2.6.16/frameworks/AWSCognito.framework/AWSCognito' was built without full bitcode. All frameworks and dylibs for bitcode must be generated from Xcode Archive or Install build file

build core

Most helpful comment

hello @awe-mt

We have fixed this issue and the updated libraries will be available in our next release.

All 5 comments

Looks like this is a duplicate of #814.

hello @awe-mt

We have fixed this issue and the updated libraries will be available in our next release.

I can confirm, trying to release got me

"ld: bitcode bundle could not be generated because './AWSCore.framework/AWSCore' was built without full bitcode. All frameworks and dylibs for bitcode must be generated from Xcode Archive or Install build file './AWSCore.framework/AWSCore' for architecture arm64"

Turning bitcode off was only solution to bypass

We have fixed it in 2.6.17. Please upgrade and let us know the feedback. Closing the issue.

Bitcode problem seems to be fixed now doing my archive.

Was this page helpful?
0 / 5 - 0 ratings