Install dependency phase of EAS looking for local IP on Android only

Hello -

I’m trying to complete an EAS build with Expo Managed Workflow after adding our privately published NPM package as a dependency. I’ve followed the steps from Private NPM Packages to add a working auth token as described. If I execute the build with the ‘–local’ flag, everything works fine. The issue only occurs on EAS cloud build. I see the NPM token is successfully copied during the “Prepare Project” phase, but it ultimately fails during “Install Dependencies” step

Running "yarn install" in the root dir of your repository 
yarn install v1.22.17
[1/4] Resolving packages...
[2/4] Fetching packages...
warning mini-css-extract-plugin@0.5.0: Invalid bin field for "mini-css-extract-plugin".
error An unexpected error occurred: "http://10.4.1.2:4873/@companydevs/company-account-logic/-/company-account-logic-1.0.2.tgz: Request failed \"404 Not Found\"".
info If you think this is a bug, please open a bug report with the information provided in "/home/expo/workingdir/build/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Error: Unknown error. See logs for more information.

Local versions: expo-cli 6.2.1
Cloud versions: expo-cli 6.0.0

It seems odd the process is attempting to call a local IP - any ideas on what’s going awry here?

you have preinstall hook that overrides yarn.lock with url to our npm cache, you need to remove it if you don’t want to use our cache

3 Likes

Yep, absolutely the case - removing the pre-install cache command we had in package.json plus adding a .yamlrc to the project root did the trick. Thank you much!

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.