ios: npm install fails EINTEGRITY

Expo Application Services (EAS)
1

android version build fine, with ios I get this error in the install dependencies phase

Running npm in the root dir of your repository 
[stderr] npm
[stderr] WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
[stderr] npm WARN
[stderr] deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
[stderr] npm WARN
[stderr] deprecated sane@4.1.0: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
[stderr] npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
[stderr] npm WARN
[stderr] deprecated uglify-es@3.3.9: support for ECMAScript is superseded by `uglify-js` as of v3.13.0
[stderr] npm
[stderr] WARN deprecated core-js@1.2.7: core-js@<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
[stderr] npm
[stderr] WARN tar zlib: incorrect data check
[stderr] npm
[stderr] WARN tarball tarball data for @react-navigation/elements@http://10.254.24.9:4873/@react-navigation/elements/-/elements-1.2.1.tgz (sha512-EnmAbKMsptrliRKf95rdgS6BhMjML+mIns06+G1Vdih6BrEo7/0iytThUv3WBf99AI76dyEq/cqLUwHPiFzXWg==) seems to be corrupted. Trying again.
[stderr] npm WARN tar zlib: incorrect data check
[stderr] npm WARN tarball tarball data for @react-navigation/elements@http://10.254.24.9:4873/@react-navigation/elements/-/elements-1.2.1.tgz (sha512-EnmAbKMsptrliRKf95rdgS6BhMjML+mIns06+G1Vdih6BrEo7/0iytThUv3WBf99AI76dyEq/cqLUwHPiFzXWg==) seems to be corrupted. Trying again.
[stderr] npm
[stderr] WARN tar TAR_ENTRY_ERROR ENOENT: no such file or directory, open '/Users/expo/workingdir/build/node_modules/@react-navigation/elements/lib/module/Header/getDefaultHeaderHeight.js'
[stderr] npm WARN tar TAR_ENTRY_ERROR ENOENT: no such file or directory, open '/Users/expo/workingdir/build/node_modules/@react-navigation/elements/lib/commonjs/Header/getHeaderTitle.js'
....

it goes on probably many TAR_ENTRY_ERROR errors
retried and got the same issue
build link for reference:

2

Im also getting this on 2 projects - one of which was sailing through 17 hours ago.

I’ve also attempted changing the cache key to no avail.

3

Having same error, was able to build project last night but not this morning.

4

Having the same problem here as well - Android builds I managed to get going again, but iOS is failing every time on installing dependencies

5

My eas android build is failing also during the “install dependencies” step.

Error:
error An unexpected error occurred: “https://registry.yarnpkg.com/colors/-/colors-1.4.2.tgz: Request failed “404 Not Found””.

6

@ctwillie package colors does not have version 1.4.2

for everyone else try clearing yarn and npm cache, delete node_modules and check if yarn/npm install works locally

1 Like
7

not sure if the voting features helps surface this issue. but please vote on this post please

8

One other thing you can try is to disable npm cache on eas by adding

"eas-build-pre-install": "npm config set registry https://registry.npmjs.org/"

in package.json scripts section

9

@wkozyra Thanks for reply.

After clearing cache, yarn install is still failing locally.

Running “yarn why colors” gives output:

Found "colors@1.4.2"
info Reasons this module exists
   - "react-native#react-native-codegen#jscodeshift" depends on it
   - Hoisted from "react-native#react-native-codegen#jscodeshift#colors"

How would I resolve this being it is a dependency of another package?

thanks,

10

@ctwillie that package does not depend on strict version, you can open your lockfile remove entry for color and return yarn/npm install

1 Like
11

Thanks! I tried clearing the npm cache, deleted the node_modules folder and ran npm install and was able to get a successful build.

The problem occurred when I changed my Bundle ID and Name to that of an existing app that I want to replace. Running a build here led to the errors I received, which persisted even when I reverted to the previous values for Bundle Id and Name - and then eventually solved when I cleared out NPM.

12

Just for other peoples ref. Triggering off the same build worked a charm so seems the cache expired or the issue is fixed.