-
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
SDK 49 - eas build ios failed on "run fastlane" #2109
Comments
I'm also having the same issue |
I am facing the same issue |
Not sure if it's related, but I had errors like that. Building without |
I am running into the same issue, works on Expo 47, iOS build fails on 48/49 but android build works. |
I don't use associatedDomains.
|
same here |
Hi, This issue seems super weird and I feel like it can be related to some issues with your credentials. Did you verify that all of your certificates are valid on the Apple Developer Portal? |
Yes, I even recreated fresh certificates, profiles and identifiers as suggested in #2024 . I didnt delete them as we are using them on another project but if it is necessary we can try |
Can you try to run a simulator build? If the issue itself is related to credentials, which sim builds don't use, it should work well. |
Yes simulator build is working well. I deleted all certificates and profiles from apple developer account. I couldn't delete Identifiers from apple developer account as I get a message "The App ID 'XXX' appears to be in use by the App Store". I ran again |
Are you using local credentials or credentials managed by EAS? |
We are using the default method which I think is managed by EAS. I can see all my certificates and keys on my expo.dev account. |
Any update? I'm going through the same thing, no solution so far. |
Going through the same issue here too |
Having same issue on SDK 46,47,49. Can't deploy at all here. Frustrating error that wasn't here 2 months ago. Any updates/workarounds? |
Got the same issue. Has anyone figured out solution ? |
@humbroll @andrewminton So I fixed this by going into app.json and changing "bundleIdentifier" to something unique. Initially just changed it to a random number (try make it as random as possible). Then later changed it to com.myname.app and it worked. I think the issue resides in that it has to be unique for some reason. I hope this works for you. |
I did it, generated new distribution certificate and provisionning profile but still got the exact same error. |
|
--non-intereactive doesnt help. We finally got a Mac (the very thing we wanted to avoid using eas...) and tried to build on it we the same result. Here is the full log of a failed build from project creation to error. We used the basic project template, expo project creation and new certificate and profile creation. It is basically :
I have no idea what other test I could do from there. I guess the error in related to something in our apple developer account but buying a new account for test purpose seems a bit much. |
|
No change |
I eventually switched to build my app from Xcode. I had some credentials/provision issues and recreated all of them in order to make it work. EAS fails with a different error now, regarding my ad-hoc credentials, but for the moment I consider building exclusively from xcode. |
Any updates about this issue ? ( Am on SDK 48 ) |
Clean Xcode project build (production => clean build folder) Close Xcode Open terminal Run cd ~/Library/Developer/Xcode/DerivedData && open . Delete all item in folder Open terminal and cd to project yarn && npx pod-install ios Open Xcode Wait to Xcode index project After Xcode finish index project => Start build (command + B) After build finish run eas build -p ios -e sit --clear-cache --local --non-interactive Please wait the xcode finish all step |
Having the same issue... tried everything in the thread but still failing at fastlane. If it helps, cloud builds and simulator builds work. |
I was able to publish on Mac using Xcode and @dattx1 steps. Build on eas still errors even when I try to use the provisioning and certificate created by Xcode. |
Hello friends,
Now it's bundling like a charm ;) But seriously the error log management is horrible! I hope it will help some of you out there... |
tried multiple possible solutions, nothing worked so far |
THIS MAN IS A GOD AMONG HUMANS. 3 days of this bullshit, thanks a lot man |
Clearing the derived data and letting the script to build it again is precisely what worked for us;
|
I have the same issue, nothing works from here |
Tried everything here but nothing works. Anyone found a solution for this? I am thinking about starting a new project with the latest expo version and copy pasting every component manually and running builds until I see something that breaks the build. |
@andreibardas |
@andreibardas any solution? I'm facing the same issue. |
@dev-shahidul
|
@VadymBezsmertnyi |
@VadymBezsmertnyi you are a savior..thanks |
I am getting this issues as well and so far all of the above comment suggestions have not worked for me. The build was working fine on SDK 49 and now not working for me anymore once upgrading to SDK 51. My dev build was perfectly fine in the expo go app. |
This worked for me, thanks. |
Same issue after upgrading to SDK 51. |
Set |
None of previous answers applied to my issue. I updated to 50 and 51 with same result. The absence of meaningful log on the run fastlane step is the real problem here, there are countless issues which can lead to the "archive failed" message and nothing of importance in the Xcode logs. I finally figured out that my problem was a duplicate key in a js object. It seems like the fastlane build for iOS fail if one object has a duplicate key which make me think it might be a lint error during build. very simple steps to reproduce:
edit _layout.tsx with
==> the app runs fine on android and iOS
==> build fail
==> build success I don't think it is normal to fail a build for a duplicate key, especially without error message. My initial project is not on typescript, only the ESLint "no-dupe-keys" rule raise a warning. |
Same here, took a few days and 50+ build attempts to locate a breaking object { error: false, error: false } in a project with about a 250K+ lines of code. Horrible experience indeed... |
Hello, were you able to resolve it? |
expo v50, I fix it! |
I'm not I have this, where can I find it so I can also delete it? |
package.json |
I don't have sentry |
oh, so just carefuly read log where maybe you will see ❌ emodji, and it will tell you what package is giving you error, in my case i saw that problem with sentry package |
work like a charm! |
Continuing to see this on SDK 51 with React Native 0.75. |
In my case, these were the things I had to do ; 1.Go to eas credentials and recreate your provisioning and distribution certificates |
Continuing to see this on SDK 51 with React Native 0.74.5 |
FWIW our issue ended up being one of our other native dependencies silently causing the error. Remove them all and then add them back one by one to determine which is the cause. |
For me i have to upgrade xcode to new ios version xD |
Build/Submit details page URL
https://expo.dev/accounts/johnfa/projects/carles-connect/builds/5f04dc92-7dbc-42c8-9f9f-bb1dac0c7b2c#run-fastlane
Summary
We started a new project with expo 49. It errors with the following message :
Build failed: The "Run fastlane" step failed with an unknown error. Refer to "Xcode Logs" below for additional, more detailed logs.
We don't see any errors in Xcode logs, I put the end of the log on the Error ouput below.
Another project on the same expo account, same computer, same ios credentials (except for provisionning) on expo 47 still builds correctly.
We don't have any Mac device to test a local build which make the issue extra-difficult to understand. We tried suggestion from #2024 and expo/expo#25105 but the error remained.
Managed or bare?
managed
Environment
expo-env-info 1.0.5 environment info:
System:
OS: Windows 10 10.0.19045
Binaries:
Node: 18.6.0 - C:\Program Files\nodejs\node.EXE
npm: 8.13.2 - C:\Program Files\nodejs\npm.CMD
npmPackages:
@expo/webpack-config: ^19.0.0 => 19.0.0
expo: ~49.0.11 => 49.0.16
react: 18.2.0 => 18.2.0
react-native: 0.72.6 => 0.72.6
react-native-web: ~0.19.6 => 0.19.9
Expo Workflow: managed
✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check npm/ yarn versions
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check that native modules do not use incompatible support packages
✔ Check for legacy global CLI installed locally
✔ Check that packages match versions required by installed Expo SDK
✔ Check that native modules use compatible support package versions for installed Expo SDK
Didn't find any issues with the project!
Error output
Build failed: The "Run fastlane" step failed with an unknown error. Refer to "Xcode Logs" below for additional, more detailed logs.
Reproducible demo or steps to reproduce from a blank project
run
eas build --platform ios
from my expo account on a project with expo ~49.0.11The text was updated successfully, but these errors were encountered: