EAS Build - Constant Issues - 500 Internal Server Error

Expo Application Services (EAS)
1

I’m experiencing constant issues with EAS Build, builds are failing at the “Install Dependencies” phase.

[stderr] npm
[stderr] ERR! code E500
[stderr] npm ERR!
[stderr] 500 Internal Server Error - GET http://10.254.24.9:4873/@firebase%2ffunctions - unknown error
[stderr] 
[stderr] npm ERR! A complete log of this run can be found in:
[stderr] npm ERR!     /Users/expo/.npm/_logs/2022-01-26T19_10_36_842Z-debug.log

This has happened before, and it eventually resolved it-self without me changing anything.

Can anyone explain what’s causing this?

2

We’re encountering this too, started recently without any changes, but weirdly only on ios builds (android has been fine). At first we started getting:

Running npm in the root dir of your repository 
[stderr] npm
[stderr] WARN tarball tarball data for react-native-reanimated@2.2.4 (sha512-Nn648MfEEnTCEiWsl1YmfkojiLyV0NMY0EiRdDRbZNfJVfxBuyqhCxI/4Jd7aBi162qpgf8XK2mByYgvF4zLrQ==) seems to be corrupted. Trying one more time.

Tried bumping the version for this dep and now get:

Running npm in the root dir of your repository 
[stderr] npm
[stderr] ERR! code E500
[stderr] npm
[stderr] ERR! 500 Internal Server Error - GET http://10.254.24.9:4873/@typescript-eslint%2fexperimental-utils - unknown error
[stderr] 
[stderr] npm ERR! A complete log of this run can be found in:
[stderr] npm ERR!     /Users/expo/.npm/_logs/2022-01-26T21_01_38_309Z-debug.log
npm exited with non-zero code: 1
1 Like
3

npm has some brief periods of downtime this morning, although it was not listed on their status page. try again and let us know if the issue persists.

4

hi, we just cleared all invalid cache entries, can you try now?

1 Like
5

One of the builds we had failed, but the most recent one got past the install step, thank you!

6

I’m attempting to create a new build, but it has been running for over half an hour and is still stuck at install dependencies. Spin up build environment took 25 minutes to complete.

Are the servers currently overloaded, or is it an issue from my side?

Build id: 6ae9b65b-7333-41d0-8bbf-9b87ec8876d1

1 Like
7

i’m not seeing this same issue on other builds. could you possibly share your project with me?

8

I’m not entirely sure how to do that, but here’s my project-id: 63d62354-932a-473d-89de-b591168ca405.

Install dependencies worked this time around, so the fix worked.

9

interesting… it seems like you have some extremely large dependencies. could you share your package.json?

10

There you go. I think I mistakenly bundled eas-cli. But that shouldn’t be that large, no? The only other variable involved, is that I just upgraded SDKs from SDK42 to SDK 44.

{
  "main": "node_modules/expo/AppEntry.js",
  "scripts": {
    "start": "expo start",
    "android": "expo start --android",
    "ios": "expo start --ios",
    "web": "expo start --web",
    "eject": "expo eject",
    "postinstall": "npx jetify"
  },
  "dependencies": {
    "@alessiocancian/react-native-actionsheet": "^3.1.1",
    "@expo/vector-icons": "^12.0.0",
    "@fortawesome/fontawesome-svg-core": "^1.2.34",
    "@fortawesome/free-brands-svg-icons": "^5.15.2",
    "@fortawesome/free-regular-svg-icons": "^5.15.2",
    "@fortawesome/free-solid-svg-icons": "^5.15.2",
    "@fortawesome/react-fontawesome": "^0.1.14",
    "@freakycoder/react-native-bounceable": "^0.2.5",
    "@react-native-async-storage/async-storage": "~1.15.0",
    "@react-native-community/blur": "^3.6.0",
    "@react-native-community/datetimepicker": "3.5.2",
    "@react-native-community/netinfo": "^6.0.2",
    "@react-native-menu/menu": "^0.5.2",
    "@react-navigation/bottom-tabs": "^6.0.8",
    "@react-navigation/native": "^6.0.5",
    "@react-navigation/stack": "^6.0.10",
    "@sentry/react-native": "^3.2.13",
    "axios": "^0.24.0",
    "eas-cli": "^0.46.0",
    "expo": "~44.0.0",
    "expo-ads-admob": "~12.0.0",
    "expo-analytics-amplitude": "~11.1.0",
    "expo-apple-authentication": "~4.1.0",
    "expo-application": "~4.0.1",
    "expo-barcode-scanner": "~11.2.0",
    "expo-constants": "~13.0.1",
    "expo-crypto": "~10.1.1",
    "expo-dev-client": "~0.8.0",
    "expo-device": "~4.1.0",
    "expo-facebook": "~12.1.0",
    "expo-file-system": "~13.1.2",
    "expo-google-app-auth": "~8.3.0",
    "expo-image-picker": "~12.0.1",
    "expo-notifications": "~0.14.0",
    "expo-sensors": "~11.1.0",
    "expo-sharing": "~10.1.0",
    "expo-status-bar": "~1.2.0",
    "expo-updates": "~0.11.5",
    "firebase": "^8.10.0",
    "install": "^0.13.0",
    "jetifier": "^2.0.0",
    "lodash": "^4.17.21",
    "lottie-react-native": "4.0.2",
    "moment": "^2.29.1",
    "moment-timezone": "^0.5.34",
    "moti": "^0.16.1",
    "react": "17.0.1",
    "react-dom": "17.0.1",
    "react-instantsearch-native": "^6.12.1",
    "react-native": "0.64.3",
    "react-native-calendars": "^1.1267.0",
    "react-native-chart-kit": "^6.11.0",
    "react-native-circular-progress": "^1.3.7",
    "react-native-flash-message": "^0.2.0",
    "react-native-gesture-handler": "~1.10.2",
    "react-native-haptic-feedback": "^1.13.0",
    "react-native-health": "^1.11.0",
    "react-native-in-app-review": "^3.3.1",
    "react-native-keyboard-aware-scroll-view": "^0.9.4",
    "react-native-modal": "^11.7.0",
    "react-native-multicolor-progress-bar": "^1.0.3",
    "react-native-purchases": "^4.5.1",
    "react-native-reanimated": "~2.3.1",
    "react-native-rounded-checkbox": "^0.3.3",
    "react-native-safe-area-context": "3.2.0",
    "react-native-segmented-picker": "^2.0.2",
    "react-native-simple-dialogs": "^1.4.0",
    "react-native-size-matters": "^0.4.0",
    "react-native-snap-carousel": "^3.9.1",
    "react-native-svg": "^12.1.1",
    "react-native-swiper": "^1.6.0-rc.3",
    "react-native-three-dots-loader": "^1.0.1",
    "react-native-web": "0.17.1",
    "rn-segmented-control": "^1.1.2",
    "sentry-expo": "^4.0.0",
    "typesense": "^1.1.2",
    "typesense-instantsearch-adapter": "^2.2.0",
    "xlsx": "^0.17.2"
  },
  "devDependencies": {
    "@babel/core": "^7.12.9"
  },
  "private": true
}
11

Similar error here, iOS only:

Running npm in the root dir of your repository 
[stderr] npm
[stderr] WARN tarball tarball data for react-native-reanimated@2.2.4 (sha512-Nn648MfEEnTCEiWsl1YmfkojiLyV0NMY0EiRdDRbZNfJVfxBuyqhCxI/4Jd7aBi162qpgf8XK2mByYgvF4zLrQ==) seems to be corrupted. Trying one more time.
12

we’re having similar issues as well for IOS only and are blocked from building via eas. We are on sdk 43.
we are able to build and run locally, and we are using the same exact version that was able to successfully build about a week ago for IOS via eas.
here’s the eas log:

[stderr] WARN tar ENOENT: no such file or directory, open '/Users/expo/workingdir/build/node_modules/.staging/expo-modules-core-001b26aa/build/Platform.d.ts'
[stderr] npm
[stderr] WARN tar ENOENT: no such file or directory, open '/Users/expo/workingdir/build/node_modules/.staging/expo-modules-core-001b26aa/build/SyntheticPlatformEmitter.d.ts'
[stderr] npm
[stderr] WARN tar ENOENT: no such file or directory, open '/Users/expo/workingdir/build/node_modules/.staging/expo-modules-core-001b26aa/build/SyntheticPlatformEmitter.web.d.ts'
[stderr] npm
[stderr] WARN tar ENOENT: no such file or directory, open '/Users/expo/workingdir/build/node_modules/.staging/expo-modules-core-001b26aa/build/errors/UnavailabilityError.d.ts'
[stderr] npm
[stderr] ERR! code EINTEGRITY
[stderr] npm ERR!
[stderr] Verification failed while extracting react-native-reanimated@2.2.4:
[stderr] npm ERR! Verification failed while extracting react-native-reanimated@2.2.4:
[stderr] npm ERR! sha512-Nn648MfEEnTCEiWsl1YmfkojiLyV0NMY0EiRdDRbZNfJVfxBuyqhCxI/4Jd7aBi162qpgf8XK2mByYgvF4zLrQ== integrity checksum failed when using sha512: wanted sha512-Nn648MfEEnTCEiWsl1YmfkojiLyV0NMY0EiRdDRbZNfJVfxBuyqhCxI/4Jd7aBi162qpgf8XK2mByYgvF4zLrQ== but got sha512-JPJAYONskR1kTdB20wJ8xhKnozeEXt1DszZmHpmBFBsMbb6USUUOv+ifLKIPecuMNLAAHlXQSU5934P1AB2BdA==. (16530409 bytes)
[stderr] 
[stderr] npm ERR! A complete log of this run can be found in:
[stderr] npm ERR!     /Users/expo/.npm/_logs/2022-01-27T01_03_35_574Z-debug.log
13

@wen-kai Can you try now?

For anyone that still see any issue like that, Currently, we just fixed all broken cache entries manually, but we are investigating root cause of the issue. If you see any issue like that please post it here and if it’s blocking you from building you can always disable cache by adding
npm config set registry https://registry.npmjs.org/ in a eas-build-pre-install hook (Integrating with third-party tooling - Expo Documentation)

2 Likes
14

@wkozyra that did the trick! thanks so much for the awesome support.