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

Unable to save turbo cache path in expo eas build #118

Open
andrewdavidcostello opened this issue Jun 19, 2024 · 1 comment
Open

Unable to save turbo cache path in expo eas build #118

andrewdavidcostello opened this issue Jun 19, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@andrewdavidcostello
Copy link

Description of the bug

How would you shortly summarise the issue?

When running an expo build there is a Save cache step due to the cache key in eas.json.

However it results in the below error.

Saving to cache:
- /Users/expo/workingdir/node_modules/.cache/turbo
ENOENT: no such file or directory, lstat '/Users/expo/workingdir/node_modules/.cache/turbo'

To Reproduce

What steps did you perform which led to this issue?

  1. Cloned down the repo
  2. Placed our native app in apps/native
  3. Triggered an expo build (this was iOS specific but imagine it applies to both)

Expected behavior

What did you expect to have happened?

The cache is saved as intended b y the defined path

Actual behavior

What did it actually result in?

Saving to cache:
- /Users/expo/workingdir/node_modules/.cache/turbo
ENOENT: no such file or directory, lstat '/Users/expo/workingdir/node_modules/.cache/turbo'

Additional context

Can you further explain the issue? E.g., information about version/environment or screenshots.

No other context unfortunately only that removing

"cache": {
        "key": "turbo",
        "paths": [
          "../../node_modules/.cache/turbo"
        ]
      },

resolved the issue. Did attempt to alter the paths to a few different levels but each time resulted in a failure.

@andrewdavidcostello andrewdavidcostello added the bug Something isn't working label Jun 19, 2024
@nathan-charles
Copy link

nathan-charles commented Aug 24, 2024

I run into this same issue I had to update path like below and seem to fix issue on eas build

"cache": {
  "key": "turbo",
  "paths": [
    "../../.turbo/cache"
  ]
},

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants