-
Notifications
You must be signed in to change notification settings - Fork 85
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
"Install dependencies" phase takes longer then expected error android eas build #2493
Comments
Hi @itajenglish, Do you know what dependency-related changes may have been introduced between commit commit f97f3b15aa065b15321f4a7dc0b15831c90b93ee (last successful Android build) and commit 9711d56049c62ca7c60ecb7b2d6b12b8de558872 (first failing one)? |
I tried to run |
I see that you are using a custom |
The only dependency changes between the first and last was the addition of |
|
Strange I ran the build locally with no issues the yarn install step only took a few seconds. I'll also note I removed the packages we have from the example package.json since you don't have a token to our repo. |
@itajenglish Thanks, can you try to run your build with {
"build": {
"production": {
"env": {
"EAS_BUILD_DISABLE_NPM_CACHE": "1"
}
}
}
} https://docs.expo.dev/build-reference/caching/#javascript-dependencies |
Build still failed unfortunately |
Can you try to run https://docs.expo.dev/build-reference/npm-hooks/#eas-build-lifecycle-hooks |
👀 So here is a head scratcher. The build with pre-hook yarn install worked. Pre hook step took 1 min & 30 seconds and the actual install step took 1 sec, I'm assuming because of cache. |
Oh, okay, it's even more confusing to me 😮 Why would I will double-check if it is possible to be some sort of networking issue, but our service health metrics are all normal and we didn't see any spikes in errors.
yeah, it makes sense |
Yep! Super strange. I will continue to test over the next few weeks as we push more releases and let you know if it starts to work again haha. |
It looks like this last build with the
|
Another update: I removed the https://expo.dev/accounts/listedb/projects/ListedB/builds/7b07dcae-cc37-4c33-ab22-e82ed8ae49a6 |
Still have issues with the install step. Any updates on what might be causing the issue @szdziedzic? |
@szdziedzic I think this issue may be linked to the new build infrastructure for Android. I turned it off in settings and my previous staging and production Android builds have been successful. I will try the new infrastructure again in our next app release to confirm this is the case and open a separate issue. Staging Build: https://expo.dev/accounts/listedb/projects/ListedB/builds/13591bf8-fb05-4e2f-9ca5-f572dc597563 |
Thanks for the updates @itajenglish!
Interesting, I believe I used old N2 machines when trying to replicate your issue, I will test it as well.
I'm really puzzled about what might be going on. I didn't see any other similar reports recently and it seems like your Android builds (when not using the cache) are using unmodified |
Hey, it seems like you have both successful and failed builds on C3D (AMD) so it doesn't seem to be related 🤔 We also didn't see any issues for C3D for other users 🤔 |
Hey @szdziedzic, I don't think it's yarn. I also tried switching to NPM in one of the builds and the install process still hung. We should be doing another build this week! Will report back on any findings. |
Hi @szdziedzic I've been facing the exact same issue for the past couple of weeks as well. Been trying the different approaches on this thread but they unfortunately have not worked out for me either. We're on: eas-cli 12.0.0 using yarn Here's the most recent one: |
This issue is stale because it has been open for 30 days with no activity. If there is no activity in the next 7 days, the issue will be closed. |
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. |
Build/Submit details page URL
https://expo.dev/accounts/listedb/projects/ListedB/builds/118ab276-82f5-428f-bb89-846ef03973d2
Summary
EAS Android builds have started to fail due to dependencies install errors. Previous internal builds with similar dependences worked as expected and now all builds internal or production are failing with this error. It only happens to Android builds and only on EAS. I've tried building locally using the EAS CLI on Mac and the build works so my guess is something is off with the Linux environment the Android builds are being created in.
Managed or bare?
Bare
Environment
Expo Env:
Expo Doctor:
Failing EAS Build Env:
Last Successful EAS Build Env: - The server size was changed but I have tested both in recent builds and both still fail
Build URL
Error output
Reproducible demo or steps to reproduce from a blank project
Package.json
The text was updated successfully, but these errors were encountered: