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

Error: No architectures in the binary. Lipo failed to detect any architectures in the bundle executable. #5463

Open
marekhac opened this issue Nov 13, 2024 · 4 comments
Labels
follow up Requires follow up from maintainers question General question

Comments

@marekhac
Copy link

Describe the bug

After updating AWSiOSSDKV2 from ver. 2.30.0 to 2.37.2 using SPM I have a problem with archiving my app on XcodeCloud. I tested my workflow with Xcode 15 and 16. Everytime I have the same error:

No architectures in the binary. Lipo failed to detect any architectures in the bundle executable.

To Reproduce
Steps to reproduce the behavior:

  1. Set AWSiOSSDKV2 to ver. 2.37.2 in Package Dependencies in the Xcode project
  2. Try to archive the app using XCodeCloud

Observed Behavior

Error on XcodeCloud:

No architectures in the binary. Lipo failed to detect any architectures in the bundle executable.

Expected Behavior
Archived build

Environment(please complete the following information):

  • SDK Version: 2.37.2
  • Dependency Manager: SPM
  • Swift Version : 5
  • Xcode Version: 15.2 & 16.1
@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 Nov 13, 2024
@edisooon edisooon added question General question and removed pending-triage Issue is pending triage pending-maintainer-response Issue is pending response from an Amplify team member labels Nov 14, 2024
@edisooon
Copy link
Member

Hi @marekhac, thank you for submitting the issue!
One of our members will take a look into this as soon as possible.
At the same time, it would be really helpful if you could provide us with full error logs

@marekhac
Copy link
Author

marekhac commented Nov 14, 2024

@edisooon Thanks for answer. Here is the fatal error part in logs associated with one of the AWS module:

Extracting arm64 from AWSCore
fatal error: lipo: input file (/Volumes/workspace/DerivedData/Build/Intermediates.noindex/ArchiveIntermediates/my_project_name/InstallationBuildProductsLocation/Applications/my_project_name.app/Frameworks/AWSCore.framework/AWSCore) must be a fat file when the -extract option is specified

@github-actions github-actions bot added the pending-maintainer-response Issue is pending response from an Amplify team member label Nov 14, 2024
@vincetran
Copy link
Member

@marekhac thanks for the error, someone will investigate this as soon as they're able to

@github-actions github-actions bot removed the pending-maintainer-response Issue is pending response from an Amplify team member label Nov 19, 2024
@vincetran vincetran added the follow up Requires follow up from maintainers label Nov 19, 2024
@harsh62
Copy link
Member

harsh62 commented Dec 10, 2024

@marekhac were you able to resolve the problem?

Apologies for the delay in getting to this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
follow up Requires follow up from maintainers question General question
Projects
None yet
Development

No branches or pull requests

4 participants