-
Notifications
You must be signed in to change notification settings - Fork 91
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 --local fails when using a Yarn 4 monorepo and Corepack #2679
Labels
needs review
Issue is ready to be reviewed by a maintainer
Comments
FezVrasta
changed the title
eas build --local fails when using a Yarn 4 monorepo
eas build --local fails when using a Yarn 4 monorepo and Corepack
Nov 8, 2024
im also running into the same issue after upgrading to expo sdk 52 |
Same issue, How do we setup up pre-build steps for eas? need to do setup yarn v4 before building. |
+1 |
1 similar comment
+1 |
I fixed it using special env:
and in package.json:
|
+1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Build/Submit details page URL
No response
Summary
I have a monorepo managed by Yarn 4.5.1, one of the workspaces is an Expo app.
When I run
eas build --local
and select Android (I can't test iOS) the build fails.Managed or bare?
managed
Environment
Error output
Reproducible demo or steps to reproduce from a blank project
It's a bit complicated to provide a repro, to reproduce the bug create a repository, init yarn workspaces with Yarn v4, then init an Expo app in a workspace, and then run
eas build --local
.I think the bug is quite obvious though, EAS is using the wrong Yarn version even though my package.json specifies the correct one and Corepack is enabled.
I noticed the same happens even if I install Yarn 4 globally, replacing Yarn 1.x. The only way around seems to be to use the internal Yarn binary loader (yarn set version) while Corepack is disabled.
The text was updated successfully, but these errors were encountered: