[iOS] Failed to find matching arch for input file
See original GitHub issueBuild/Submit details page URL
Summary
We ran into this error upgrading our application from SDK 41 to 44. It happens again on the blank template created by expo init my-project
. We’re getting this error trying to run the build on the Simulator, and it has previously been rejected by Apple. We never got this issue before.
Managed or bare?
managed
Environment
expo-env-info 1.0.2 environment info: System: OS: Linux 5.13 Ubuntu 20.04.4 LTS (Focal Fossa) Shell: 5.8 - /usr/bin/zsh Binaries: Node: 12.22.7 - ~/.nvm/versions/node/v12.22.7/bin/node npm: 8.3.1 - ~/.nvm/versions/node/v12.22.7/bin/npm npmPackages: expo: ~44.0.0 => 44.0.6 react: 17.0.1 => 17.0.1 react-dom: 17.0.1 => 17.0.1 react-native: 0.64.3 => 0.64.3 react-native-web: 0.17.1 => 0.17.1 npmGlobalPackages: eas-cli: 0.49.0 expo-cli: 5.3.0 Expo Workflow: managed
Error output
No response
Reproducible demo or steps to reproduce from a blank project
expo init my-project
eas build
Issue Analytics
- State:
- Created a year ago
- Comments:9 (2 by maintainers)
Hi @kelley-sharp thanks for your response.
The issue is that our application has been refused multiple times by Apple Store, for a crash in iPads it seems. We have been able to reproduce this issue, by downloading our builds and trying to put it on the iPad simulator, which gives us the
Failed to find matching arch for input file
as shown on the screenshot Hugo added. We are guessing that the issue is coming from code signing.We tried it again today, by using
eas build
on a Linux machine, after wiping certificates both on EAS and Apple servers, which means that all certificates have been created by EAS. The build can be found here: https://expo.dev/accounts/louis-energic/projects/energic-v2/builds/e1e7a8b2-ed57-4d49-9234-0ddebb08683fThe details given by Apple:
Locally,
expo doctor
gives me no warning. Below the results ofeas diagnostics
.Dependencies
eas.json
This issue was closed because it has been inactive for 7 days since being marked as stale. Please open a new issue if you believe you are encountering a related problem.