cli: Unable to resolve module `./debugger-ui/ui.cc464243.js` from ``

Solved it for me in two ways:

First I simply removed the sourceMappingURL from the mentioned files, as these seemed to raise the error (build problems?). But as I had to redo this on any package update / addition (which got quite annoying, as you might have guessed ; ), I was quite happy that @react-native-community/cli-debugger-ui v4.7.0 has been released yesterday! So I quickly added the following to my package.json:

  "resolutions": {
    "@react-native-community/cli-debugger-ui": "4.7.0"
  }

Now, after deleting yarn.lock, running react-native clean-project-auto (the same could have been accomplished by deleting node_modules, cleaning the individual builds & pods, but react-native-clean-project is so much neater % ) & running yarn again, the problem was gone. (Be sure to remove the resolution, when RN updates again…)

Hope it helps anyone!

Best,

Tim.

Obviously, I was testing with the debugger on. I was able to reproduce your issues upon applying diff you provided. I was able to fix this issue by starting the debugger with --reset-cache flag. Tell me if this fixes your issue.

@VitaliyGaliy Got this issue and manage to fix it by deleting yarn.lock then run yarn install. It may got some version conflict when upgrading packages.

I’m using npx to run the app, not sure whether I can pass --reset-cache flag with that.

this was the solution for me https://stackoverflow.com/a/60755519/1557613

hi, i have try using "resolutions": { "@react-native-community/cli-debugger-ui": "4.7.0" }

but still disable ability touchable, ex: onPress is not working, but if not in debug mode, it working normaly

So, you should try delete package-lock file then run npm install again

this was the solution for me https://stackoverflow.com/a/60755519/1557613

Hard refresh of the debugger window also worked for me (cmd + shift + r)

its been bloddy 9 months and no solution yet?! wtf!

watchman watch-del-all - didnt solve my problem. In console I have

No difference, it happens even with a new created react native app npx react-native init MyTestApp

MAP ./index.js ░░░░░░░░░░░░░░░░ 0.0% (0/1)Error: Unable to resolve module ./debugger-ui/debuggerWorker.d9da4ed7.js from ``:

None of these files exist:

• debugger-ui/debuggerWorker.d9da4ed7.js(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
• debugger-ui/debuggerWorker.d9da4ed7.js/index(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)

this is such a mess, does anyone actually have a fix?

I ran npm start -- --reset-cache and then started the app using react-native run-ios, but the issue still exists. Previously I used npx react-native run-ios to run the app.

Will it be possible for you to list the commands I need to execute? So that I can do a retry.

Same issue here, no solution worked with RN 0.62.2

Same problem here with file debuggerWorker.cff11639.js ! None of the above solutions worked for me.

sigh, this is depressing

faced the same and solved by just restarting the bundler with --reset-cache.

yarn start --reset-cache

Having the same issue after upgrading to Expo SDK 38 and RN 0.62. None of the suggested fixes have worked.

This still happens to me. Tried all the solutions: https://stackoverflow.com/a/60755519/1557613 https://github.com/react-native-community/cli/issues/1081#issuecomment-614223917 https://github.com/react-native-community/cli/issues/1081#issuecomment-609648148 https://github.com/facebook/react-native/issues/28531#issuecomment-617101194

I fixed it by disabling remote debugger and reenabling it.

I’m experiencing a similar issue after upgrading from react-native 0.61.5 to 0.62.2

Error: Unable to resolve module `./debugger-ui/debuggerWorker.cff11639` from ``:

It’s reproducible in an existing project and a new project from template, but it only occurs on a physical device. In the simulator, debug mode works fine. Even with one packager instance running, the simulator will behave correctly and the physical device experiences the issue.

watchman watch-del-all && npm start -- --reset-cache and removing package-lock.json and yarn.lock have not made a difference.

On my end this error evolved after an upgrade to ReactNative 0.64.0, now i get this one in a terminal

Error: EISDIR: illegal operation on a directory, read
    at Object.readSync (fs.js:592:3)
    at tryReadSync (fs.js:366:20)
    at Object.readFileSync (fs.js:403:19)
    at UnableToResolveError.buildCodeFrameMessage (/Users/victorsheyanov/code/expert-guidion-app/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:347:17)
    at new UnableToResolveError (/Users/victorsheyanov/code/expert-guidion-app/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:333:35)
    at ModuleResolver.resolveDependency (/Users/victorsheyanov/code/expert-guidion-app/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:211:15)
    at DependencyGraph.resolveDependency (/Users/victorsheyanov/code/expert-guidion-app/node_modules/metro/src/node-haste/DependencyGraph.js:413:43)
    at /Users/victorsheyanov/code/expert-guidion-app/node_modules/metro/src/lib/transformHelpers.js:317:42
    at /Users/victorsheyanov/code/expert-guidion-app/node_modules/metro/src/Server.js:1471:14
    at Generator.next (<anonymous>)

Chrome console:

And it’s true, debuggerWorker.aca173c4.js.map is not present in a build directory, only .js:

I checked with our team (Mac + Ubuntu OS), none of them has this .js.map file requested by Chrome when debugging and all of us has same error (either unable to resolve... or illegal operation on a directory...) that is cause by ChromeDebugger requesting 1 file: http://localhost:8081/debugger-ui/debuggerWorker.aca173c4.js.map

I did stick a console.log in a place where this error is thrown: result:

Obviously /Users/victorsheyanov/code/expert-guidion-app/debugger-ui/debuggerWorker.aca173c4.js is incorrect path as it should be /Users/victorsheyanov/code/expert-guidion-app/node_modules/@react-native-community/cli-debugger-ui/build/ui/debuggerWorker.aca173c4.js

Any ideas what module can cause this problem?

PS. just to be clean, requesting .map file causes this error with debuggerWorker.aca173c4.js: PPS: debugging works anyway, but this scary error as annoying as hell…

After updating to RN 63.0, I still get the error, but the app compiles nonetheless and is debuggable.

Unfortunately none of the above solutions work for me 😢

I encountered the same issue, so far I’ve been working only with the iOS simulator

RN version:

"react": "16.13.1",
"react-native": "0.63.3",

what worked for me was removing the app from the simulator and installing it again

Still no fix for this? Should we go flutter now?

Nothing mentioned here solved my issue. I’m having this both on Android and iOS.

The error log is: ui.bcd3f9d1.js:16 GET http://localhost:8081/debugger-ui/debuggerWorker.cff11639.js 404 (Not Found)

And there are following errors in debugger network:

Still no progress in this? We are nearly in April… Really sad for a production framework.

Solved it for me in two ways:

First I simply removed the sourceMappingURL from the mentioned files, as these seemed to raise the error (build problems?). But as I had to redo this on any package update / addition (which got quite annoying, as you might have guessed ; ), I was quite happy that @react-native-community/cli-debugger-ui v4.7.0 has been released yesterday! So I quickly added the following to my package.json:

  "resolutions": {
    "@react-native-community/cli-debugger-ui": "4.7.0"
  }

Now, after deleting yarn.lock, running react-native clean-project-auto (the same could have been accomplished by deleting node_modules, cleaning the individual builds & pods, but react-native-clean-project is so much neater % ) & running yarn again, the problem was gone. (Be sure to remove the resolution, when RN updates again…)

Hope it helps anyone!

Best,

Tim.

I resolved this issue by install version "@react-native-community/cli-debugger-ui": "3.0.0"

For expo users, I think you accidently turned on Live Debugging in Expo, Just clear Expo’s Cache and Data from your Phone, and everything will be back to normal.

Thank you so much!!! saved my project

Same Error. RN version: 0.63.2

For expo users, I think you accidently turned on Live Debugging in Expo, Just clear Expo’s Cache and Data from your Phone, and everything will be back to normal.

I solved this issue, check your app name

AppRegistry.registerComponent(‘realmapp’, () => appContainer)

app name was the issue in my case

In expo app, I resolve by install react-native-debugger-open

yarn add -D react-native-debugger-open

And add this script to package.json, use yarn debug to start expo dev server.

"debug": "REACT_DEBUGGER=\"rndebugger-open --open --expo\" expo start"

With --expo flag, react-native-debugger-open auto use expo’s correct port.

Turn on Debug Remote JS in expo app, react-native-debugger will auto launch, and redux-devtools is work.

I use in expo 39 and react-native-debugger installed. Both redux-devtools-extension and window.__REDUX_DEVTOOLS_EXTENSION__ are work.

If someones having the problem still, try using react-navigation v4. I had v5 and downgraded it to v4 and it worked.

Running “empty cache and hard reload” on the debugger page in Chrome as mentioned here fixes the issue for me.

I should mention that this is happening to my iOS build

I’m experiencing this issue on both 0.62.0 and 0.62.2

Error: Unable to resolve module ./debugger-ui/ui.7beef9ab.css from ``:

None of the above-mentioned methods have worked. I have checked and file node_modules/@react-native-community/cli-debugger-ui/build/ui/ui.7beef9ab.css exists

Disabling debugging makes simulator load bundle, but only a white screen is displayed until Bundle location is changed to localhost:8081 and app is restarted Then app works until debugging is enabled again

Solved it by uninstalling the app on the emulator / device then build the app again.

I added “resolutions” but it didn’t help.

"resolutions": {
   "@react-native-community/cli-debugger-ui": "4.7.0"
 },

After that I did “yarn add react-devtools-core” and the error went away.

I got same the issue. when I open the debugger in the console I am getting this error. I spent more to debug this error.

Solution I used resolutions in the package.json.

"resolutions": {
   "@react-native-community/cli-debugger-ui": "4.7.0"
 },

then I deleted package-lock.json and node_modules. then I reinstalled node modules, synced with the android studio. clean the project. Finally, used react-native run-android

this was the solution for me https://stackoverflow.com/a/60755519/1557613

Hard refresh of the debugger window also worked for me (cmd + shift + r)

This worked for me too!

Hi all, I found I encountered this error when I had a bug in one my of components, not related to the debugger. My debugger window (http://localhost:8081/debugger-ui/) was open. I checked it and sure enough there was a console error that led me to the real issue.

Same issue, the only solution who worked for me was to downgrade React native …

Do they exist though? Running watchman watch-del-all may help in such occasions, to clear watcher cache and re-crawl files

–reset-cache and manually uninstalling app from emulator worked for me.

This problem I resolved by stoping debugging remote JS in expo app.

have the same problem’ non of the above helps.

specific Error

Error: Unable to resolve module ./debugger-ui/ui.bcd3f9d1.js from ``:

None of these files exist:

• debugger-ui\ui.bcd3f9d1.js(.native|.native.expo.ts|.expo.ts|.native.expo.tsx|.expo.tsx|.native.expo.js|.expo.js|.native.expo.jsx|.expo.jsx|.native.ts|.ts|.native.tsx|.tsx|.native.js|.js|.native.jsx|.jsx|.native.json|.json|.native.wasm|.wasm)
• debugger-ui\ui.bcd3f9d1.js\index(.native|.native.expo.ts|.expo.ts|.native.expo.tsx|.expo.tsx|.native.expo.js|.expo.js|.native.expo.jsx|.expo.jsx|.native.ts|.ts|.native.tsx|.tsx|.native.js|.js|.native.jsx|.jsx|.native.json|.json|.native.wasm|.wasm) at ModuleResolver.resolveDependency (C:\Users\yadin\DoneWithIt2\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:163:15) at ResolutionRequest.resolveDependency (C:\Users\yadin\DoneWithIt2\node_modules\metro\src\node-haste\DependencyGraph\ResolutionRequest.js:52:18) at DependencyGraph.resolveDependency (C:\Users\yadin\DoneWithIt2\node_modules\metro\src\node-haste\DependencyGraph.js:287:16) at C:\Users\yadin\DoneWithIt2\node_modules\metro\src\lib\transformHelpers.js:267:42 at Server.<anonymous> (C:\Users\yadin\DoneWithIt2\node_modules\metro\src\Server.js:841:41) at Generator.next (<anonymous>) at asyncGeneratorStep (C:\Users\yadin\DoneWithIt2\node_modules\metro\src\Server.js:99:24) at _next (C:\Users\yadin\DoneWithIt2\node_modules\metro\src\Server.js:119:9)

Still no fix for this? Should we go flutter now?

On my side the issue cause by react-native-reanimated@2, I removed it and the issue disappear. maybe try to check your libs

For expo users, I think you accidently turned on Live Debugging in Expo, Just clear Expo’s Cache and Data from your Phone, and everything will be back to normal.

@chandan1602

I tried uninstalling the app on the simulator and reinstalling. That didnt help. Is there another way to clear cache and data from the expo app?

Do you get the same error now, my method was plain and simple, i just opened the app info, and from there i cleared the app cache and data, also i ran expo r -c and collectively that worked for me

@timhagn solution of setting the resolutions to RN debugger CLI version 4.7.0 and installing that specific version worked for me. I’m using RN v0.62.2. I also reset the cache after npm install and before re-running with npx.

After deleting my cache and reloading chrome it didn’t help, I even tried to restart my pc and nothing of course. But then today it started working again without me doing anything. Really strange

Just try all the ways I found still failed, the easiest one for me is to clone the repository, install and build again.

For me, what fixed it was removing

"plugins": [
    "@babel/plugin-proposal-class-properties"
  ]

from my babel.config.js. None of the other methods worked.

No idea why this fixes it but hey, it works!

Yes, this occurs for me in both an existing project updated to 0.62.2 and a clean-slate project initialized from react-native init. I actually went as far as removing every app signed by this developer profile from the device and reinstalling, and it still occurs.

I filed a more thorough report here, since the on-device error leads me to believe its react-native related more than it is debugger related.

I didn use yarn this time. Just npm install from the first start on the new OS.