-
Notifications
You must be signed in to change notification settings - Fork 84
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
EAS Build failing iOS production builds #2058
Comments
hi there! I would recommend fixing the doctor warning about the config plugins version misalignment. that may be related. in general, this guide is a useful place to go for troubleshooting these issues: https://docs.expo.dev/build-reference/troubleshooting/ if you're still stuck after that, there are some tips on the bottom of the guide for getting further help |
Hello @brentvatne , I fixed the issues mentioned by the doctor warning and tried to create another build, but still failing for the same reason: build --> https://expo.dev/accounts/quantoz/projects/qbs-test-app/builds/cbd4e230-b06e-4383-b139-b802ce0d7e0e npx expo-doctor
expo-env-info
|
I solved it, my issue was the way in which I handled some env variables. I was using the EXPO_PUBLIC prefix and somehow removing it made it work, when using them inside the app.config.ts file |
Build/Submit details page URL
https://expo.dev/accounts/quantoz/projects/qbs-test-app/builds/fbf0460d-bf13-410d-8f73-3d1fcd5d1a15
Summary
Note: the Android app builds correctly with this config, it's an iOS issue
The iOS production build fails with the following:
Some context:
After upgrading to Expo SDK 49, I have refactored my project to use different env files, per environment and also whether it has to be used locally or for builds. I have the following:
I used
eas secret
to upload the latter two in order to be used also for builds, since they contain secrets I don't want in my repo.I just added two more env files:
These are uploaded to the repo, and they contain info on package name, app name... Note: the app name is exactly the same as before
My eas.json:
app.config.ts:
Managed or bare?
Managed
Environment
Error output
Reproducible demo or steps to reproduce from a blank project
Not easy to do so, but I provided my whole config and can provide more
The text was updated successfully, but these errors were encountered: