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

Build failed for arm64e: Amplify.swiftmodule is not built for arm64e #3893

Open
CarlosJaimes opened this issue Oct 7, 2024 · 6 comments
Open
Labels
build Issues related to build and CI/CD feature-request Request a new feature pending-maintainer-response Issue is pending response from an Amplify team member

Comments

@CarlosJaimes
Copy link

CarlosJaimes commented Oct 7, 2024

Describe the bug

When trying to build my iOS application for arm64e, the build fails with the error message: Build failed because Amplify.swiftmodule is not built for arm64e. Please try a run destination with a different architecture.

I am following Apple's documentation for enabling Pointer Authentication (PAC) as per Apple's documentation. The error occurs after configuring the app to build with the arm64e architecture in Xcode and trying to archive the build.

The issue is preventing me from using security features provided by the arm64e architecture, and it seems that the current version of the Amplify framework is not compatible with this architecture.

Screenshot 2024-10-07 at 10 44 39 AM

Steps To Reproduce

1 - Follow Apple's instructions for enabling arm64e and Pointer Authentication (PAC) from Apple Documentation. (https://developer.apple.com/documentation/security/preparing-your-app-to-work-with-pointer-authentication) 

2 - In Xcode, go to Build Settings and add arm64e to the Architectures section under $(ARCHS_STANDARD) and the Excluded Architectures field should remain empty.

3 - Import AWS Amplify in your project:
import Amplify
import AWSAPIPlugin
import AWSCognitoAuthPlugin

4 - In the AppDelegate or SceneDelegate, initialize the AWS Amplify library:

func configureAmplify() {
    do {
        try Amplify.add(plugin: AWSCognitoAuthPlugin())
        try Amplify.add(plugin: AWSAPIPlugin())
        try Amplify.configure()
        print("Amplify configured successfully")
    } catch {
        print("Failed to configure Amplify: \(error)")
    }
}

5 - Build the app targeting arm64e architecture.
6 - The build will fail with the error: Amplify.swiftmodule is not built for arm64e.

Expected behavior

The application should build successfully for arm64e architecture without throwing errors. I expect AWS Amplify and its related modules to support the arm64e architecture to allow for Pointer Authentication (PAC) on newer devices.

Amplify Framework Version

2.42.1

Amplify Categories

API, DataStore

Dependency manager

Swift PM

Swift version

5.0

CLI version

12.12.6

Xcode version

16.0 (16A242d)

Relevant log output

Build failed because Amplify.swiftmodule is not built for arm64e. Please try a run destination with a different architecture.

Is this a regression?

Yes

Regression additional context

No response

Platforms

iOS

OS Version

17

Device

iPad Pro M4/ iPad Pro M2

Additional context

This issue prevents the app from building with arm64e, which is necessary to enable Pointer Authentication (PAC) as required for additional security on newer devices. We rely heavily on AWS Amplify for data synchronization, and this is a critical blocker for compliance with our security requirements.

@github-actions github-actions bot added pending-triage Issue is pending triage pending-maintainer-response Issue is pending response from an Amplify team member labels Oct 7, 2024
@thisisabhash thisisabhash added build Issues related to build and CI/CD and removed pending-triage Issue is pending triage pending-maintainer-response Issue is pending response from an Amplify team member labels Oct 8, 2024
@thisisabhash
Copy link
Member

Hello, Thank you for posting this issue. Our team will take a look and post updates here.

@thisisabhash thisisabhash added the bug Something isn't working label Oct 8, 2024
@CarlosJaimes
Copy link
Author

Thank you very much, I will be very attentive. That is a critical security point that my application must solve.

@github-actions github-actions bot added the pending-maintainer-response Issue is pending response from an Amplify team member label Oct 8, 2024
@ruisebas ruisebas removed the pending-maintainer-response Issue is pending response from an Amplify team member label Oct 9, 2024
@CarlosJaimes
Copy link
Author

Any Update...?

@github-actions github-actions bot added the pending-maintainer-response Issue is pending response from an Amplify team member label Nov 1, 2024
@ruisebas ruisebas added feature-request Request a new feature and removed bug Something isn't working labels Nov 1, 2024
Copy link
Contributor

github-actions bot commented Nov 1, 2024

This has been identified as a feature request. If this feature is important to you, we strongly encourage you to give a 👍 reaction on the request. This helps us prioritize new features most important to you. Thank you!

@ruisebas
Copy link
Member

ruisebas commented Nov 1, 2024

Hey @CarlosJaimes, we don't have any updates to report at this moment.

Since this is something that is currently not supported, I've tagged this as a feature request

@github-actions github-actions bot removed the pending-maintainer-response Issue is pending response from an Amplify team member label Nov 1, 2024
@CarlosJaimes
Copy link
Author

Any Update...?

@github-actions github-actions bot added the pending-maintainer-response Issue is pending response from an Amplify team member label Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Issues related to build and CI/CD feature-request Request a new feature pending-maintainer-response Issue is pending response from an Amplify team member
Projects
None yet
Development

No branches or pull requests

3 participants