SHA-1 for file ... is not computed when using resolver.resolveRequest

[vjpr]

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

I am using a custom resolver.resolveRequest function in rn-cli.config.js. See https://facebook.github.io/metro/docs/en/configuration#resolver-options.

The error message is being printed from metro/src/node-haste/DependencyGraph.js#getSha1, which is being called by metro/src/Bundler.js#transformFile:

metro/src/node-haste/DependencyGraph.js#getSha1

  getSha1(filename: string): string {
    const resolvedPath = fs.realpathSync(filename);
    const sha1 = this._hasteFS.getSha1(resolvedPath);
    if (!sha1) {
      throw new ReferenceError(`SHA-1 for file ${filename} is not computed`);
    }
    return sha1;
  }

The issue is that the file won't exist in the haste map if you are resolving it in the resolveRequest hook.

If the current behavior is a bug, please provide the steps to reproduce and a minimal repository on GitHub that we can yarn install and yarn test.

https://github.com/vjpr/expo-v2-test-pnpm/tree/broken

You need to run pnpm install (the reason for the custom resolver is because symlinks are not supported by metro and hence cause problems for pnpm).

What is the expected behavior?

getSha1 should compute hash if not in haste map.

Please provide your exact Metro configuration and mention your Metro, node, yarn/npm version and operating system.

[email protected]
[email protected]
[email protected]

Workaround

Add to metro/src/node-haste/DependencyGraph.js#getSha1:

    if (!sha1) {
      return getFileHash(resolvedPath)
      function getFileHash(file) {
        return require('crypto')
          .createHash('sha1')
          .update(fs.readFileSync(file))
          .digest('hex')
      }
    }

I have released a patched version here: Use [email protected]

[Stephen2]

I got this when trying to get Expo to work with yarn workspaces, using expo-yarn-workspaces

[pavermakov]

I've got the same issue when I tried to upgrade react-native to 0.57.0. I followed the steps mentioned the change log (https://github.com/react-native-community/react-native-releases/blob/master/CHANGELOG.md#057), but had no luck.

[mareksuscak]

@Stephen2 me too, did you solve it?

[Stephen2]

Sorry, moved to different project

[ekmobile]

This is still a problem today with "react-native": "^0.59.2". Will there be real fix or do we need to copy/paste the workaround?

• BUNDLE_FILE=/Users/.../Library/Developer/Xcode/DerivedData/...-aexneivqfarcnddyzdbcbwoienmj/Build/Products/Release-iphoneos/....app/main.jsbundle
• node /Users/.../git/...-app-react-native/.../node_modules/react-native/cli.js bundle --entry-file index.js --platform ios --dev false --reset-cache --bundle-output /Users/.../Library/Developer/Xcode/DerivedData/...-aexneivqfarcnddyzdbcbwoienmj/Build/Products/Release-iphoneos/....app/main.jsbundle --assets-dest /Users/.../Library/Developer/Xcode/DerivedData/...-aexneivqfarcnddyzdbcbwoienmj/Build/Products/Release-iphoneos/....app
  warning: the transform cache was reset.
  Loading dependency graph, done.
  error SHA-1 for file /Users/.../git/...-app-react-native/.../node_modules/metro/src/lib/polyfills/require.js (/Users/.../git/...-app-react-native/.../node_modules/metro/src/lib/polyfills/require.js) is not computed
• [[ false != true ]]
• [[ ! -f /Users/.../Library/Developer/Xcode/DerivedData/...-aexneivqfarcnddyzdbcbwoienmj/Build/Products/Release-iphoneos/....app/main.jsbundle ]]
• echo 'error: File /Users/.../Library/Developer/Xcode/DerivedData/...-aexneivqfarcnddyzdbcbwoienmj/Build/Products/Release-iphoneos/....app/main.jsbundle does not exist. This must be a bug with'
  error: File /Users/.../Library/Developer/Xcode/DerivedData/...-aexneivqfarcnddyzdbcbwoienmj/Build/Products/Release-iphoneos/....app/main.jsbundle does not exist. This must be a bug with
• echo 'React Native, please report it here: https://github.com/facebook/react-native/issues'
  React Native, please report it here: https://github.com/facebook/react-native/issues
• exit 2

[nick-michael]

For anyone seeing this error when using expo-yarn-workspaces, I got this and fixed it by simply deleting the auto-generated file (the file that the error points to) and deleting all the node modules and then just running yarn again to re-install node modules and re-generate the file.

[ghost]

I am experiencing this on RN 0.60.5

[dioptre]

Also fixes RN 0.61

[ghost]

Also fixes RN 0.61

Do you mean that on RN 0.61 it is working as expected?

[donholly]

Seeing the same issue as described on 0.60.5. The workaround provided by @vjpr works - thank you! Looks like #455 should fix this. I'm curious why doesn't seem to be a bigger problem for everyone 😄

I made the change in ~/.config/yarn/global/node_modules/metro/src/node-haste/DependencyGraph.js

[dioptre]

@dusan-dragon I needed the @vjpr fix to get RN 0.61 to work.

[ricick]

I'm having this issue on a windows 10 machine here. Same project on another dev machine with the same version of node doesn't display the issue.

[ikbal99]

put all files inside assets name of folder something like this

../../assets/beach.jpg

[vj-raghavan]

@donholly I am not sure why no one is flagging this issue more. I have just run in to this issue after I have setup a new terminal and cleaned up all my old node modules.

Thanks to @vjpr workaround it worked after rebuilding the app. Is this a miss on our part ? or is this being actively looked into ?

[mhers91]

put all files inside assets name of folder something like this

../../assets/beach.jpg

This worked for me ikbal99

[Gerlison]

Works for me, 0.61.5

[nkraev]

0.61.5 indeed works.
I also did npm i -g react-native-cli - it updated cli to 2.0.1 version and bundling worked.

[bkhurjawal]

I solved this issue by using yarn start instead of starting project with react-native start(it uses npm start).
I have been adding dependencies in project using Yarn add {dependencyName} and starting project via npm. which created error of SHA-1.

[ricick]

I found it was an issue with me accessing the project on a second drive via a symlink on C: rather than navigating to the D: drive

[f4th4n]

I fixed it by install correct react-native-cli:

yarn global remove react-native
yarn global add react-native-cli

[martinfrouin]

Thanks @f4th4n it works for me

[finghtingjie]

I had tried all the methods above but still not work for me.
OS:mac Catalina
node:13.3.0
watchman:4.9.0
react-native:0.61.5

the error log like this

Metro Bundler has encountered an error: SHA-1 for file /Users/.../Downloads/AwesomeProject/node_modules/metro/src/lib/polyfills/require.js (/Users/.../Downloads/AwesomeProject/node_modules/metro/src/lib/polyfills/require.js) is not computed

[MohamedHamedLab]

i had the same issue and fix it by following this steps
1- updating metro-react-native-babel-preset to version 0.57.0
2- resetCache: true in metro.config
3- removeing node modules & yarn lock file and reinstall

[rpcarnell]

The solution offered by @vjpr worked like a charm.

[khomchyk]

Hello!
Are there any plans to fix this issue or support searching for symlinks?

The patch suggested by @vjpr is working, but it will be better to have an official support of this functionality.

[agelessZeal]

npm i -g react-native-cli
It is solution of this issue.

[rad182]

If anyone else having issue when archiving ios.
I had to install react-native-cli and use it.
yarn add react-native-cli
then override CLI_PATH

[huzaifaaak]

I am getting this issue on rn-tester app on android. None of the above is working for me

[JulesGuesnon]

Hi there !

My case is probably unlikely: the folder containing the project had .zip in the name and was causing the issue.

I checked the code and there's a specific case for .zip files in getSha1 which caused the error

[vjpr]

If you are using pnpm, see pnpm/pnpm#3731.

[zaidraddad94]

you ar the man

[muganwas]

put all files inside assets name of folder something like this

../../assets/beach.jpg

This worked for me, thanks!

[Qazafi-Dev]

i am having this issue while generating debug apk! why?

[patricksantos-bcs]

If anyone else having issue when archiving ios. I had to install react-native-cli and use it. yarn add react-native-cli then override CLI_PATH

This one works for me! Thanks!

[Vednus]

Just an FYI: was having this issue when running codepush and fixed it by restarting my machine.

[instanceof-inf]

None of the above worked for me, the only thing that worked was checking the 'For install builds only' checkbox under 'Bundle React Native code and images' under Build Phases

[fwielstra]

Just an addition, I ran into this issue today; at first I thought it was due to having pages and routers of my app spread across different libraries using NX, which uses a symlink to node_modules in every app project.

However, the issue was that I already had Metro running in another terminal tab, and kept trying to remove node_modules and restart the app (and Metro) in another tab.

TL;DR make sure there are no other Metro processes running when you try anything described in this thread.

[kennethkeim]

Just an FYI: was having this issue when running codepush and fixed it by restarting my machine.

Machine restart fixed my issues too.

TL;DR make sure there are no other Metro processes running when you try anything described in this thread.

It may be that I had a metro process running in the background that got disconnected from my terminal emulator.

[dezoxel]

I solved this issue by using yarn start instead of starting project with react-native start(it uses npm start). I have been adding dependencies in project using Yarn add {dependencyName} and starting project via npm. which created error of SHA-1.

I have the same issue.
React Native v0.71.2.

Running thru yarn start solves the issue, thanks a lot!

[lukasgjetting]

Started working again after I ran watchman watch-del '{PROJECT_DIR}' where {PROJECT_DIR} is the root directory of your RN project, i.e. /Users/lukas/projects/myapp

[yoannes]

RN 0.72.3

I'm using yarn workspaces and the following worked for me:

  "workspaces": {
    "packages": [
      "packages/*"
    ],
    "nohoist": [
      "**/react-native",
      "**/react-native/**",
      "**/@react-native",
      "**/@react-native/**"
    ]
  },