Skip to content
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_PROJECT_ROOT variable no longer seem to work in monorepo setup #2938

Open
TowhidKashem opened this issue Mar 9, 2025 · 1 comment
Open
Labels
needs review Issue is ready to be reviewed by a maintainer

Comments

@TowhidKashem
Copy link

Build/Submit details page URL

No response

Summary

I have an expo app in the subfolder of a mono repo setup (yarn workspaces). I haven't changed my deploy command or project structure which is the same as always and it's always worked fine. But today I tried to deploy and got some errors at the install stage, I clicked around and noticed that my entire repo had been uploaded to expo and not just the project subfolder like it usually is the case.

So I ran the eas inspect command to see what's actually being uploaded and sure enough the generated folder contained the whole repo.

Did anything change in a recent version that could have broken the use of this env var? I can confirm the other var I'm using EAS_NO_VCS is working because I see the yellow warning message like usual:

Using EAS CLI without version control system is not recommended, use this mode only if you know what you are doing.

My npm scripts:

"eas:inspect": "yarn pre-deploy && EAS_NO_VCS=1 EAS_PROJECT_ROOT=. eas build:inspect --platform ios --
"deploy:ios:dev": "yarn pre-deploy && EAS_NO_VCS=1 EAS_PROJECT_ROOT=. eas build --platform ios --clear-cache --profile development && yarn post-deploy"
profile production --stage archive --output ./eas.tmp --force && yarn post-deploy",
"pre-deploy": "tzx ../../scripts/tools/prepost-deploy.ts --predeploy",
"post-deploy": "tzx ../../scripts/tools/prepost-deploy.ts --postdeploy",

Managed or bare?

Managed

Environment

  expo-env-info 1.2.2 environment info:
    System:
      OS: macOS 15.3.1
      Shell: 5.9 - /bin/zsh
    Binaries:
      Node: 20.18.3 - /opt/homebrew/opt/node@20/bin/node
      Yarn: 1.22.22 - /opt/homebrew/bin/yarn
      npm: 10.8.2 - /opt/homebrew/opt/node@20/bin/npm
      Watchman: 2025.03.03.00 - /opt/homebrew/bin/watchman
    Managers:
      CocoaPods: 1.16.2 - /Users/towhidkashem/.rbenv/shims/pod
    SDKs:
      iOS SDK:
        Platforms: DriverKit 24.2, iOS 18.2, macOS 15.2, tvOS 18.2, visionOS 2.2, watchOS 11.2
    IDEs:
      Xcode: 16.2/16C5032a - /usr/bin/xcodebuild
    npmPackages:
      expo: ~52.0.35 => 52.0.37 
      react: 18.3.1 => 18.3.1 
      react-native: 0.76.7 => 0.76.7 
    Expo Workflow: managed
npx expo-doctor
Need to install the following packages:
[email protected]
Ok to proceed? (y) y

15/15 checks passed. No issues detected!

Error output

No response

Reproducible demo or steps to reproduce from a blank project

See message.

@TowhidKashem TowhidKashem added the needs review Issue is ready to be reviewed by a maintainer label Mar 9, 2025
@TowhidKashem
Copy link
Author

TowhidKashem commented Mar 9, 2025

Update: I just found a workaround, if I use the absolute path of the project folder on my computer e.g. EAS_PROJECT_ROOT=/Users/foo/path/to/project/folder instead of the EAS_PROJECT_ROOT=. relative path, it works. I'll leave the issue open in case it helps tracking the regression but if you think it's not worth it feel free to close, the workaround is good enough solution for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs review Issue is ready to be reviewed by a maintainer
Projects
None yet
Development

No branches or pull requests

1 participant