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

I'm also having the same issue when run on debug mode.

Same issue "react-native": "0.62.2",

Same issue "react-native": "0.62.2",

same

Same issue.

My React versions :

"react": "16.11.0",
"react-native": "0.62.2"

Any solutions?

I believe it's something with react-native-config. I have the same issue here:

    "react": "16.11.0",
    "react-native": "0.62.2",
    "react-native-config": "^1.2.0",

@jmlavoier I have the same issue, but don't use react-native-config.

"react": "16.11.0",
"react-native": "0.62.2",

Same issue "react-native": "0.62.2",

same

https://reactnavigation.org/docs/troubleshooting/#app-is-not-working-properly-when-connected-to-chrome-debugger

I have the same issue:

    "react": "16.11.0",
    "react-native": "0.62.2",

@imamrobani Thanks for the link. But it doesn’t address the issue?

The issue may well be Chrome related. But it wasn’t there in earlier versions of React-Native.

Same here, weird that it stopped working tonight.
It's not allowing, in Android device at least, to press the TouchableOpacity component using onPress. It seems to work for the first time, some interaction of my app work once, but then stops to work.

❯ react-native info
info Fetching system and libraries information...
System:
    OS: macOS 10.15.3
    CPU: (8) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz
    Memory: 17.99 MB / 8.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 13.7.0 - ~/.nvm/versions/node/v13.7.0/bin/node
    Yarn: 1.21.1 - /usr/local/bin/yarn
    npm: 6.13.6 - ~/.nvm/versions/node/v13.7.0/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.9.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
    Android SDK:
      API Levels: 27, 28
      Build Tools: 27.0.3, 28.0.3
      Android NDK: Not Found
  IDEs:
    Android Studio: Not Found
    Xcode: 11.3.1/11C504 - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_231 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.11.0 => 16.11.0 
    react-native: 0.62.2 => 0.62.2 
  npmGlobalPackages:
    *react-native*: Not Found

I uninstalled completely the app from my device, and it turned it back to work without the error 🤔 (Android device)

@imamrobani Thanks for the link. But it doesn’t address the issue?

The issue may well be Chrome related. But it wasn’t there in earlier versions of React-Native.

in my case I use

"react": "16.11.0",
"react-native": "0.62.2",
"react-navigation": "^4.0.10"

the problem is when I use the actual device in mode debugging my apps can't navigation to another screen. but if use emulator is running well.
Does anyone know where the problem is?

previously I used react native 0.61 just fine

It is happening everytime I switch from debugging from bash to chrome, while it's showing the logs in metro bundler, and I click debug in the rn menu

edit:
it's basically forcing us to use the metro bundler, and not chrome to debug.
When I set the app from the menu to debug mode, when javascript logs are going to the browser console, I receive this error

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

None of these files exist:
  * debugger-ui/debuggerWorker.cff11639.js(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
  * debugger-ui/debuggerWorker.cff11639.js/index(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
    at ModuleResolver.resolveDependency (/Users/henriquederosa/dev/myapp/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:163:15)
    at ResolutionRequest.resolveDependency (/Users/henriquederosa/dev/myapp/node_modules/metro/src/node-haste/DependencyGraph/ResolutionRequest.js:52:18)
    at DependencyGraph.resolveDependency (/Users/henriquederosa/dev/myapp/node_modules/metro/src/node-haste/DependencyGraph.js:287:16)
    at /Users/henriquederosa/dev/myapp/node_modules/metro/src/lib/transformHelpers.js:267:42
    at Server.<anonymous> (/Users/henriquederosa/dev/myapp/node_modules/metro/src/Server.js:841:41)
    at Generator.next (<anonymous>)
    at asyncGeneratorStep (/Users/henriquederosa/dev/myapp/node_modules/metro/src/Server.js:99:24)
    at _next (/Users/henriquederosa/dev/myapp/node_modules/metro/src/Server.js:119:9

It is happening everytime I switch from debugging from bash to chrome, while it's showing the logs in metro bundler, and I click debug in the rn menu

edit:
it's basically forcing us to use the metro bundler, and not chrome to debug.
When I set the app from the menu to debug mode, when javascript logs are going to the browser console, I receive this error

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

None of these files exist:
  * debugger-ui/debuggerWorker.cff11639.js(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
  * debugger-ui/debuggerWorker.cff11639.js/index(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
    at ModuleResolver.resolveDependency (/Users/henriquederosa/dev/myapp/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:163:15)
    at ResolutionRequest.resolveDependency (/Users/henriquederosa/dev/myapp/node_modules/metro/src/node-haste/DependencyGraph/ResolutionRequest.js:52:18)
    at DependencyGraph.resolveDependency (/Users/henriquederosa/dev/myapp/node_modules/metro/src/node-haste/DependencyGraph.js:287:16)
    at /Users/henriquederosa/dev/myapp/node_modules/metro/src/lib/transformHelpers.js:267:42
    at Server.<anonymous> (/Users/henriquederosa/dev/myapp/node_modules/metro/src/Server.js:841:41)
    at Generator.next (<anonymous>)
    at asyncGeneratorStep (/Users/henriquederosa/dev/myapp/node_modules/metro/src/Server.js:99:24)
    at _next (/Users/henriquederosa/dev/myapp/node_modules/metro/src/Server.js:119:9

Yes, it's exactly like this, I have uninstalled and install again but still same when debugging mode

Same here, weird that it stopped working tonight.
It's not allowing, in Android device at least, to press the TouchableOpacity component using onPress. It seems to work for the first time, some interaction of my app work once, but then stops to work. ```

Hi @HenriqueDerosa, can you please check this issue - is it similar to that's happening to you on an Android device when debugging?
https://github.com/facebook/react-native/issues/29083#issuecomment-642457919

Hey All, I had this issue and what worked for me was just clearing my Google Chrome cache.

And by 'worked' I mean that I didn't get the red error screen over my simulator & I could continue developing as normal.

Any Solution for this? I am not able to debug application. Breakpoint is not hitting

Any solution to this? It seems it happens on React Native 0.62.2 even if you create a fresh project. For some reason there is an error 500 when you look at the debugger.

Any solution to this? It seems it happens on React Native 0.62.2 even if you create a fresh project. For some reason there is an error 500 when you look at the debugger.

just skip it, it doesn't matter as long as it doesn't cause application error

When this is happening, I can no longer input text into text fields, as the keyboard doesn't appear. The debugger becomes unusable, not being able to login into the application.

When this is happening, I can no longer input text into text fields, as the keyboard doesn't appear. The debugger becomes unusable, not being able to login into the application.

try it on emulator

When this is happening, I can no longer input text into text fields, as the keyboard doesn't appear. The debugger becomes unusable, not being able to login into the application.

try it on emulator

On emulator it is working, but the error is still thrown in the bundler. Why is it affecting only device debugging?

When this is happening, I can no longer input text into text fields, as the keyboard doesn't appear. The debugger becomes unusable, not being able to login into the application.

try it on emulator

On emulator it is working, but the error is still thrown in the bundler. Why is it affecting only device debugging?

when I use the actual device (Android 9) it's not working, then I change the device to under android 9, in my case I use Android 6 it's working

When this is happening, I can no longer input text into text fields, as the keyboard doesn't appear. The debugger becomes unusable, not being able to login into the application.

try it on emulator

On emulator it is working, but the error is still thrown in the bundler. Why is it affecting only device debugging?

when I use the actual device (Android 9) it's not working, then I change the device to under android 9, in my case I use Android 6 it's working

You mean you change the emulated device to android 6 API or use an older device for debugging? Nevertheless, this shouldn't happen and the debugger should work on newer devices as well ...

Resolved for me by hard refreshing (shift + refresh) the React debugger tab in Chrome, then clearing application data in inspector, then finally restarting the main bundler thread in bash (npm start)

Same problem here. As soon as the Debug mode is activated, it seems the app stops registering all onPress() events. scrolling is still possible.

The problem doesn't occur within the emulator. However, the same error is still shown in the console and terminal (react server).

react-native -v returns

react-native-cli: 2.0.1
react-native: 0.62.2

I've been having this issue as well. Searching high and low for an answer.
Disabling my ad-blocker gave me more feedback in the console for some reason.
And then I noticed chrome was debugging the main thread. Easy to overlook.

After clicking the debuggerWorker thread, the app started registering and hitting breakpoints...
I hope this helps some of you out 👍

"react": "16.11.0",
"react-native": "0.62.2",

I have the same issue:

Thanks @HenriqueDerosa - Completely uninstalling and re-installing the Expo app worked for me too.

Of interest, I had just upgraded from SDK 36 to 38 and upgraded expo-cli as well. So perhaps there is a problem with transitioning both at a time. Also I believe my profile had remote-debug automatically enabled by default in the last App install. Maybe it doesn't cause problem if it's disabled at first and then you go to enable it later?? Either way, thanks for your tip!

Same issue for the past week. Cannot develop. Incredibly frustrating. This should be caught by the teams making the upgrades.

"react": "~16.11.0",
"react-dom": "~16.11.0",
"react-native": "https://github.com/expo/react-native/archive/sdk-38.0.1.tar.gz",

same here, and my simulator auto-refresh

for me : react-native-meteor issue - to be exact the "eventemitter3" node module has removed setMaxListeners

Any news? I got the same issue

I'm using Chrome Debugger on a real iOS device and it appears I was able to fix by disabling all my Chrome extensions...one of them must have been interfering. I no longer see the error or have unresponsive touches while debugging

@chadwhittaker Indeed, removing Redux Tools from Chrome made the touch to work again. It might be related to that extension.

Has anyone found a solution yet? This is ridiculous.... Tried literally everything and still here

The solution is to make the Date and Time of your machine (in case of iOS) and Emulator (in case of Android). I'm getting this same error, and in console it says **Debugger and device times have drifted by more than 60s. Please correct this by running adb shell "datedate +%m%d%H%M%Y.%S" on your debugger machine.**

After updating the Date and Time of emulator it works.

@zenkhas Yes, at least for me on an emulator it functions properly even without adjusting the date and time but there are certain cases where using a physical device for development purposes is crucial.

So far I've tried meddling with the node modules, deleting all types of caches (including the browser's... every browser's tbh so we can rule out the issue being browser-specific), adjusting the date and time, ruling out possible browser extensions that might be messing with the debugging process, swapping debugger threads and so on... :/

FYI for what it's worth I use Windows 10 and Chrome (Android development v0.62.2)

Hey guys I'm getting the same here

React Native version mismatch.

JavaScript version: 0.63.0
Native version: 0.62.2

Make sure that you have rebuilt the native code. If the problem persists try clearing the Watchman and packager caches with watchman watch-del-all && react-native start --reset-cache.

followed by this in expo

ERROR
00:18
Error: Unable to resolve module ./debugger-ui/debuggerWorker.cff11639.js from ``:

can't run the debugger on the android emulator.

anyone have any luck. Im using windows 10 and Chrome as well.

To come back on my previous post. After 2 weeks of searching I found the solution regarding the missed onPress() events when de remote debugger is active. This followed from a few seconds of timing difference between my phone and laptop. Disabling auto disabling automatic time resolution on my phone and manually setting the time on my phone back a minute solved this problem for me.
Credits for pointing in the right direction to: https://github.com/facebook/react-native/issues/27008#issuecomment-592048282

But the same Error: Unable to resolve module remains when activating the remote debugger. Which results in the phone being unable to auto refresh after changes been saved in the code. After the first update you get the Refreshing... message on the phone. The refresh doesn't happen, no additional error/warning printed in the console. After following updates the message is not printed on the phone anymore. However, I get the console logs printed.

The weird thing is that my colleague has pretty much the same Arch Linux + ThinkPad set-up. On his devices the problem doesn't occur. We invested many many hours in attempting to locate the problem, without results. So, for now I just manually reload the app from the terminal after every save when the debugger is activated. Which of course has a severe impact on productivity.

$ react-native --version
4.8.0
(installed with yarn, but also tried npm)

Resolved for me by hard-refreshing (shift + refresh) the React debugger tab in Chrome, then clearing application data in the inspector, then finally restarting the main bundler thread in bash (npm start)

Very easy answer...

Has anyone found a solution yet? This is ridiculous.... Tried literally everything and still here

Resolved for me by hard-refreshing (shift + refresh) the React debugger tab in Chrome, then clearing application data in the inspector, then finally restarting the main bundler thread in bash (npm start)

Has anyone found a solution yet? This is ridiculous.... Tried literally everything and still here

Resolved for me by hard-refreshing (shift + refresh) the React debugger tab in Chrome, then clearing application data in the inspector, then finally restarting the main bundler thread in bash (npm start)

Tried this many times. Doesn't resolve it for me.

Is SHIFT+F5 OK in this window?

I solved my problem:

in package.json

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

delete yarn.lock and run yarn install.

After update from RN v0.61.4 to RN v0.63.1.

I made the following steps:

1. Clear caches: watchman watch-del-all; rm -rf $TMPDIR/metro-*; rm -rf $TMPDIR/haste-map-*;
2. Remove yarn.lock, node_modules and install packages: rm yarn.lock; rm -rf node_modules; yarn;
3. Add the following resolutions to package.json:

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

After that, I executed project in simulator and everything is okay. ✨

same problem.

same problem

The problem still exist on react-native 0.63.1

same problem

Edit: i stopped remote debugging in expo client and it worked

I had same problem with following version
"react": "16.11.0",
"react-native": "0.62.2",

Below step work for me

Try this:

• Stop application if running
• Close remote debug tab
• run again

Similar problem for me. I see this in the react-native console window when I open the developer console in the Chrome tab containing the debugger UI http://localhost:8081/debugger-ui/ after selecting Debug in the in-app developer menu on a physical Android device:

info Launching Dev Tools...
Error: Unable to resolve module `./debugger-ui/ui.bcd3f9d1.js` from ``:

None of these files exist:
  * debugger-ui\ui.bcd3f9d1.js(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
  * debugger-ui\ui.bcd3f9d1.js\index(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
    at ModuleResolver.resolveDependency (C:\Users\Chase\company\companyMobile\projects\mobile\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:163:15)
    at ResolutionRequest.resolveDependency (C:\Users\Chase\company\companyMobile\projects\mobile\node_modules\metro\src\node-haste\DependencyGraph\ResolutionRequest.js:52:18)
    at DependencyGraph.resolveDependency (C:\Users\Chase\company\companyMobile\projects\mobile\node_modules\metro\src\node-haste\DependencyGraph.js:287:16)
    at C:\Users\Chase\company\companyMobile\projects\mobile\node_modules\metro\src\lib\transformHelpers.js:267:42
    at Server.<anonymous> (C:\Users\Chase\company\companyMobile\projects\mobile\node_modules\metro\src\Server.js:841:41)
    at Generator.next (<anonymous>)
    at asyncGeneratorStep (C:\Users\Chase\company\companyMobile\projects\mobile\node_modules\metro\src\Server.js:99:24)
    at _next (C:\Users\Chase\company\companyMobile\projects\mobile\node_modules\metro\src\Server.js:119:9)
Error: Unable to resolve module `./debugger-ui/ui.7beef9ab.css` from ``:

None of these files exist:
  * debugger-ui\ui.7beef9ab.css(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
  * debugger-ui\ui.7beef9ab.css\index(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
    at ModuleResolver.resolveDependency (C:\Users\Chase\company\companyMobile\projects\mobile\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:163:15)
    at ResolutionRequest.resolveDependency (C:\Users\Chase\company\companyMobile\projects\mobile\node_modules\metro\src\node-haste\DependencyGraph\ResolutionRequest.js:52:18)
    at DependencyGraph.resolveDependency (C:\Users\Chase\company\companyMobile\projects\mobile\node_modules\metro\src\node-haste\DependencyGraph.js:287:16)
    at C:\Users\Chase\company\companyMobile\projects\mobile\node_modules\metro\src\lib\transformHelpers.js:267:42
    at Server.<anonymous> (C:\Users\Chase\company\companyMobile\projects\mobile\node_modules\metro\src\Server.js:841:41)
    at Generator.next (<anonymous>)
    at asyncGeneratorStep (C:\Users\Chase\company\companyMobile\projects\mobile\node_modules\metro\src\Server.js:99:24)
    at _next (C:\Users\Chase\company\companyMobile\projects\mobile\node_modules\metro\src\Server.js:119:9)
Error: Unable to resolve module `./debugger-ui/debuggerWorker.cff11639.js` from ``:

None of these files exist:
  * debugger-ui\debuggerWorker.cff11639.js(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
  * debugger-ui\debuggerWorker.cff11639.js\index(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
    at ModuleResolver.resolveDependency (C:\Users\Chase\company\companyMobile\projects\mobile\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:163:15)
    at ResolutionRequest.resolveDependency (C:\Users\Chase\company\companyMobile\projects\mobile\node_modules\metro\src\node-haste\DependencyGraph\ResolutionRequest.js:52:18)
    at DependencyGraph.resolveDependency (C:\Users\Chase\company\companyMobile\projects\mobile\node_modules\metro\src\node-haste\DependencyGraph.js:287:16)
    at C:\Users\Chase\company\companyMobile\projects\mobile\node_modules\metro\src\lib\transformHelpers.js:267:42
    at Server.<anonymous> (C:\Users\Chase\company\companyMobile\projects\mobile\node_modules\metro\src\Server.js:841:41)
    at Generator.next (<anonymous>)
    at asyncGeneratorStep (C:\Users\Chase\company\companyMobile\projects\mobile\node_modules\metro\src\Server.js:99:24)
    at _next (C:\Users\Chase\company\companyMobile\projects\mobile\node_modules\metro\src\Server.js:119:9)

Version information:

# Windows 10 64-bit
$ react-native -v
react-native-cli: 2.0.1
react-native: 0.62.2

My app was updated from react-native 0.60.0 to react-native 0.62.2 about two months ago.

This error breaks debugging on physical Android devices. Specifically, after the error is logged, many UI interactions in the app break such that the app becomes unusable. However, I am able to debug on Android emulators, despite the same error happening on emulators.

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

None of these files exist:

• debugger-ui/debuggerWorker.cff11639(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
• debugger-ui/debuggerWorker.cff11639/index(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
  at ModuleResolver.resolveDependency (/Users/sergeinepryakhin/Documents/Projects/RNoverview/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:163:15)
  at ResolutionRequest.resolveDependency (/Users/sergeinepryakhin/Documents/Projects/RNoverview/node_modules/metro/src/node-haste/DependencyGraph/ResolutionRequest.js:52:18)
  at DependencyGraph.resolveDependency (/Users/sergeinepryakhin/Documents/Projects/RNoverview/node_modules/metro/src/node-haste/DependencyGraph.js:287:16)
  at /Users/sergeinepryakhin/Documents/Projects/RNoverview/node_modules/metro/src/lib/transformHelpers.js:267:42
  at /Users/sergeinepryakhin/Documents/Projects/RNoverview/node_modules/metro/src/Server.js:1096:37
  at Generator.next ()
  at asyncGeneratorStep (/Users/sergeinepryakhin/Documents/Projects/RNoverview/node_modules/metro/src/Server.js:99:24)
  at _next (/Users/sergeinepryakhin/Documents/Projects/RNoverview/node_modules/metro/src/Server.js:119:9)
  at processTicksAndRejections (internal/process/task_queues.js:97:5)

Same problem. No one solution helped to resolve this. But it looks like this mistake do not prevent me to debug in Chrome. But it kills VSCode terminal.
"react": "16.13.1",
"react-native": "0.63.0",

Hey, I just started a new expo project with expo-cli and tried the remote debugging on expo-cli. I've got the same error/warning messages. Moreover, the chrome debugging console didn't show the code error location in the code. Rather, it shows some weird location in the build bundle file which is of no use in real debugging. I am wondering if this behavior is linked to these errors and has anybody had semilar experience? To demonstrate, I've added a console.log('abc') in app.js and this is what is printed in the debug console

abc node_modules%5Cexpo%5CAppEntry.bundleplatform=android&dev=true&minify=false&hot=false

Errors:
DevTools failed to load SourceMap: Could not load content for http://localhost:19001/debugger-ui/ui.bcd3f9d1.js.map: HTTP error: status code 500, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load SourceMap: Could not load content for http://localhost:19001/debugger-ui/ui.7beef9ab.css.map: HTTP error: status code 500, net::ERR_HTTP_RESPONSE_CODE_FAILURE
Here is my Expo diagnostic

Expo CLI 3.23.0 environment info:
System:
OS: Windows 10 10.0.18362
Binaries:
Node: 10.16.0 - C:\Program Files\nodejs\node.EXE
npm: 6.14.6 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: Version 4.0.0.0 AI-193.6911.18.40.6626763
npmPackages:
expo: ~38.0.8 => 38.0.8
react: ~16.11.0 => 16.11.0
react-dom: ~16.11.0 => 16.11.0
react-native: https://github.com/expo/react-native/archive/sdk-38.0.2.tar.gz => 0.62.2
react-native-web: ~0.11.7 => 0.11.7

Please just clear your react native project...

Same here, I guess we will just need to live with that.. :/

Everything was working fine on my project until this error appears and now, I'm stuck like all of you :thinking:

I have just discovered that this error disappears when i change my main App to a functional component instead of a class component.

please how to solve this problems ? im even fresh install from react native init and still get this problem

I stopped remote debugging in expo client and it worked, im gonna use the web browser to fix stuff

Lol go away stupid bot!

Same error (in remote debugging), I have just updated to Expo 38
I have three device (Android 7, Android 8 and iOS 13.3). All of them have this error while remote debugging. I can interact with app on Android 8 and iOS , but on Android 7 - no, onPress event doesn't work. It seems like RN issue and not expo.

Same Error. RN Version: 0.63.2

Disabling cache on the network tab in chrome can help

...but not always. I'm pretty sure this issue is what causes the "debugging loads old builds" problem where fast refresh updates your code but upon app reload you end up with an old cached version. That was a fun one to discover.... The state of react-native profiling tools and debugging tools (especially with Android emulator) is pretty sad at the moment but unfortunately I don't have the experience with native code to improve them.

edit: I wonder if this is related to https://github.com/facebook/react-native/issues/29424 ? Although that happens when not debugging as well.

Same error here.

It's definitely an error relative to sourcemaps. When you try to fetch the url for the sourcemaps it will dump that error. If you disable sourcemaps for both js and css in devtools settings, it won't show any more errors. I'd say that it's either not generating or not serving them?

Anyone knows why could that be? In my case it's happening in Windows

This issue comes up randomly for me, and when it does, it does not want to go away. BUT this just worked for me. Although a little time consuming, I'll be doing this from now on as a worst case scenario:

1. Close Chrome and Quit. Update chrome if needed.
2. Close the app on iPhone
3. Stop & close Xcode
4. Delete the app from my phone
5. Run npx react-native clean-project to (I tell it to wipe node_modules, pods, clean build folders, and clean cache)
6. Restart my Macbook

Obviously if you're running on simulator you'll have to adjust the process slightly.

I fixed this error by correct a css style error in style sheet.
I have a css style sheet with value displayed as below, the justifyContent's value caused this error. After correct the value of justifyContent, my app successfully loaded.
loginOrCreateTabContainer:{ flexDirection: "row", justifyContent: "stretch", },

I'm seeing the identical issue on iOS after upgrading my project to RN 0.63.2 from 0.61.

I still see the same problem with a brand new empty project created with react-native init.

I've spent the better part of two days on this, trying every suggested solution above without success. I even tried a brand new MacBook running macOS 10.15.5, setting up the needed dev tools with the latest version of everything-- same issue.

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

None of these files exist:
  * debugger-ui/debuggerWorker.cff11639(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
  * debugger-ui/debuggerWorker.cff11639/index(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
    at ModuleResolver.resolveDependency (/Users/jeremy/Developer/source/MyCep-Upgrade/MyCep/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:163:15)
    at ResolutionRequest.resolveDependency (/Users/jeremy/Developer/source/MyCep-Upgrade/MyCep/node_modules/metro/src/node-haste/DependencyGraph/ResolutionRequest.js:52:18)
    at DependencyGraph.resolveDependency (/Users/jeremy/Developer/source/MyCep-Upgrade/MyCep/node_modules/metro/src/node-haste/DependencyGraph.js:287:16)
    at /Users/jeremy/Developer/source/MyCep-Upgrade/MyCep/node_modules/metro/src/lib/transformHelpers.js:267:42
    at /Users/jeremy/Developer/source/MyCep-Upgrade/MyCep/node_modules/metro/src/Server.js:1096:37
    at Generator.next (<anonymous>)
    at asyncGeneratorStep (/Users/jeremy/Developer/source/MyCep-Upgrade/MyCep/node_modules/metro/src/Server.js:99:24)
    at _next (/Users/jeremy/Developer/source/MyCep-Upgrade/MyCep/node_modules/metro/src/Server.js:119:9)
    at process._tickCallback (internal/process/next_tick.js:68:7)

$ react-native info
info Fetching system and libraries information...
System:
    OS: macOS 10.15.5
    CPU: (8) x64 Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
    Memory: 1.19 GB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 10.22.0 - ~/.nvm/versions/node/v10.22.0/bin/node
    Yarn: Not Found
    npm: 6.14.6 - ~/.nvm/versions/node/v10.22.0/bin/npm
    Watchman: 4.7.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.8.4 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.6, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK:
      API Levels: 20, 23, 24, 25, 26, 27, 28
      Build Tools: 23.0.1, 23.0.3, 25.0.0, 25.0.2, 25.0.3, 26.0.0, 26.0.1, 26.0.2, 27.0.0, 27.0.1, 27.0.2, 27.0.3, 28.0.3, 29.0.0
      System Images: android-24 | Google Play Intel x86 Atom, android-25 | Google APIs Intel x86 Atom, android-26 | Google Play Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 3.3 AI-182.5107.16.33.5314842
    Xcode: 11.6/11E708 - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_131 - /usr/bin/javac
    Python: 2.7.15 - /usr/local/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1 
    react-native: 0.63.2 => 0.63.2 
  npmGlobalPackages:
    *react-native*: Not Found

I run RN 0.63.2 on macOS 10.15.6 with IOS emulator. And I struggle with that error for at least 6 months in a row. Here is what helps me every time I get stack:

**1. Restart your mac

1. $ react-native start --reset-cache
2. Run app from the XCode**

Tips:

• once you miss to run "react-native start --reset-cache" and started your project from XCode without it, you may catch "Unable to resolve module" and the only what can help you is a Holy System Restart)
• every time development is finished I do: cmd+C on terminal, cmd+Q on emulator, then Stop (cmd+.) on XCode, close debugger tab in Chrome

Hope that workaround will help someone! GL

I run RN 0.63.2 on macOS 10.15.6 with IOS emulator. And I struggle with that error for at least 6 months in a row. Here is what helps me every time I get stack:

1. Restart your mac 2. $ react-native start --reset-cache 3. Run app from the XCode

Tips:

• once you miss to run "react-native start --reset-cache" and started your project from XCode without it, you may catch "Unable to resolve module" and the only what can help you is a Holy System Restart)
• every time development is finished I do: cmd+C on terminal, cmd+Q on emulator, then Stop (cmd+.) on XCode, close debugger tab in Chrome

Hope that workaround will help someone! GL

After that I go to the church and put some candles on, draw some pentograms, and dance with a tambourine for 2-3 hours. :) :) :)
I solved it by stop using this debugger and start using react native debugger application.

I was facing this issue in android.I tried everything mentioned above but nothing worked. Later i found that i have installed a dependency but that wasn't configured properly that was causing the issue.In my case it was react-native-firebase as I haven't configured it properly yet so i removed that after that i was able to run the app with enabling debugger.

Facing the same issue

using "react-native": "0.62.2"

No cache reset or reboot fixed the issue

Reverting back to react-native 0.23.1 from 0.62.2 solved it for me

Weird one. The workaround posted by @HenriqueDerosa worked fine for me (Uninstall and Install the app on the device)

Context:
This error appeared when I was trying to make a GET request on my application hosted locally

try {
     api.get('/projects').then(response => {   //api has the baseUrl/Computer Ip
        console.log("Done!");
     });
} catch (error) {
     console.log(error);
}

Error:

index.bundle?platfor…&minify=false:41548 Possible Unhandled Promise Rejection (id: 1):
Error: Network Error
Error: Network Error
    at createError (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:99384:17)
    at EventTarget.handleError (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:99288:16)
    at EventTarget.dispatchEvent (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:32277:27)
    at EventTarget.setReadyState (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:31367:20)
    at EventTarget.__didCompleteResponse (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:31183:16)
    at http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:31293:47
    at RCTDeviceEventEmitter.emit (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:3537:37)
    at MessageQueue.__callFunction (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:2765:31)
    at http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:2497:17
    at MessageQueue.__guard (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:2719:13)

Same issue.
React-native version is 0.61.5
No recommendations from above helped

Update:
For me, Redux was the reason for that trouble, try to figure out if everything is set up and your store has all needed values

Same issue on android device
Error: Unable to resolve module `./debugger-ui/ui.bcd3f9d1.js` from: ``
I tried every step but nothing works. Using android 9.0 image to debug and react-native 0.63.2

Same

+1

The problem seems to be related to React Native Debugger in Chrome. I reinstalled the Expo client on the emulator and then start the app, the problem is gone. Just dont't choose the Dubug Remote JS option.

https://reactnavigation.org/docs/troubleshooting/#app-is-not-working-properly-when-connected-to-chrome-debugger

Hey All, I had this issue and what worked for me was just clearing my Google Chrome cache.

And by 'worked' I mean that I didn't get the red error screen over my simulator & I could continue developing as normal.

ı solved for me . thanks

Weird one. The workaround posted by @HenriqueDerosa worked fine for me (Uninstall and Install the app on the device)

Context:
This error appeared when I was trying to make a GET request on my application hosted locally

try {
     api.get('/projects').then(response => {   //api has the baseUrl/Computer Ip
        console.log("Done!");
     });
} catch (error) {
     console.log(error);
}

Error:

index.bundle?platfor…&minify=false:41548 Possible Unhandled Promise Rejection (id: 1):
Error: Network Error
Error: Network Error
    at createError (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:99384:17)
    at EventTarget.handleError (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:99288:16)
    at EventTarget.dispatchEvent (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:32277:27)
    at EventTarget.setReadyState (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:31367:20)
    at EventTarget.__didCompleteResponse (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:31183:16)
    at http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:31293:47
    at RCTDeviceEventEmitter.emit (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:3537:37)
    at MessageQueue.__callFunction (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:2765:31)
    at http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:2497:17
    at MessageQueue.__guard (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false:2719:13)

Uninstalling on the emulator did the trick for me

I have resolve this by React Native Debug "Stop Debugging" and “Debug”

Crashe the debugger-ui/ EXPO-CLI
React-native expo SDK 39
DevTools failed to load SourceMap: Could not load content for http://localhost:19001/debugger-ui/ui.bcd3f9d1.js.map: HTTP error: status code 500, net::ERR_HTTP_RESPONSE_CODE_FAILURE

Faced the same issue. Installing the lastest version of watchman helped me
https://facebook.github.io/watchman/docs/install.html

Faced the same issue. Installing the lastest version of watchman helped me
https://facebook.github.io/watchman/docs/install.html

@vovka-s still no luck even though I have installed the latest version(4.9.0) of watchmen and only run a new inited rn app by
react-native init itdidaAppCompany

macOS 10.15.7
RN: 0.63.2

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

None of these files exist:
  * debugger-ui/ui.bcd3f9d1.js(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
  * debugger-ui/ui.bcd3f9d1.js/index(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
    at ModuleResolver.resolveDependency (/Users/forrest/Downloads/itdidaAppCompany/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:163:15)
    at ResolutionRequest.resolveDependency (/Users/forrest/Downloads/itdidaAppCompany/node_modules/metro/src/node-haste/DependencyGraph/ResolutionRequest.js:52:18)
    at DependencyGraph.resolveDependency (/Users/forrest/Downloads/itdidaAppCompany/node_modules/metro/src/node-haste/DependencyGraph.js:287:16)
    at /Users/forrest/Downloads/itdidaAppCompany/node_modules/metro/src/lib/transformHelpers.js:267:42
    at Server.<anonymous> (/Users/forrest/Downloads/itdidaAppCompany/node_modules/metro/src/Server.js:841:41)
    at Generator.next (<anonymous>)
    at asyncGeneratorStep (/Users/forrest/Downloads/itdidaAppCompany/node_modules/metro/src/Server.js:99:24)
    at _next (/Users/forrest/Downloads/itdidaAppCompany/node_modules/metro/src/Server.js:119:9)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)

Faced the same issue. Installing the lastest version of watchman helped me
https://facebook.github.io/watchman/docs/install.html

@vovka-s still no luck even though I have installed the latest version(4.9.0) of watchmen and only run a new inited rn app by
react-native init itdidaAppCompany

macOS 10.15.7
RN: 0.63.2

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

None of these files exist:
  * debugger-ui/ui.bcd3f9d1.js(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
  * debugger-ui/ui.bcd3f9d1.js/index(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
    at ModuleResolver.resolveDependency (/Users/forrest/Downloads/itdidaAppCompany/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:163:15)
    at ResolutionRequest.resolveDependency (/Users/forrest/Downloads/itdidaAppCompany/node_modules/metro/src/node-haste/DependencyGraph/ResolutionRequest.js:52:18)
    at DependencyGraph.resolveDependency (/Users/forrest/Downloads/itdidaAppCompany/node_modules/metro/src/node-haste/DependencyGraph.js:287:16)
    at /Users/forrest/Downloads/itdidaAppCompany/node_modules/metro/src/lib/transformHelpers.js:267:42
    at Server.<anonymous> (/Users/forrest/Downloads/itdidaAppCompany/node_modules/metro/src/Server.js:841:41)
    at Generator.next (<anonymous>)
    at asyncGeneratorStep (/Users/forrest/Downloads/itdidaAppCompany/node_modules/metro/src/Server.js:99:24)
    at _next (/Users/forrest/Downloads/itdidaAppCompany/node_modules/metro/src/Server.js:119:9)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)

I am using Windows 10 && react-native : latest
Same issue occurs for me also. Even after installing the watchman, @react-native-community/cli-debugger-ui & react-devtools-core.
Nothing worked

I recommend using this , for debug
https://github.com/jhen0409/react-native-debugger

I'm using expo and I upgraded to sdk-38.0.2 and this left me unable to use remote debugging. My app would load the login page but all the buttons and inputs would be unresponsive. But now and again after clicking the button many times the button would eventually work. The app works fine when remote debugging is disabled. Had to go back to expo's react native sdk-36.0.1 and expo 36.0.2.

Not working
package.json
"expo": "^38.0.0",
"react-native": "https://github.com/expo/react-native/archive/sdk-38.0.2.tar.gz",
package-lock.json
Expo: 38.0.10

Working
package.json
"expo": "^36.0.0",
"react-native": "https://github.com/expo/react-native/archive/sdk-36.0.1.tar.gz",
package-lock.json
Expo: 36.0.2

package.json Not Working
```{
"main": "node_modules/expo/AppEntry.js",
"scripts": {
"start": "expo start",
"android": "expo start --android",
"ios": "expo start --ios",
"eject": "expo eject",
"lint": "eslint . -c .eslintrc.js --ext .js",
"flow": "flow",
"publish-updates": "expo publish",
"build-android-apk": "expo build:android -t apk",
"build-android-aab": "expo build:android -t app-bundle",
"build-ios": "expo build:ios"
},
"dependencies": {
"@expo/vector-icons": "^10.0.0",
"@react-native-community/masked-view": "0.1.10",
"@react-navigation/drawer": "^5.0.0",
"@react-navigation/native": "^5.0.0",
"@react-navigation/stack": "^5.0.0",
"expo": "^38.0.0",
"expo-linear-gradient": "~8.2.1",
"expo-notifications": "~0.3.3",
"expo-permissions": "~9.0.1",
"lodash": "^4.17.20",
"moment": "^2.24.0",
"prop-types": "^15.7.2",
"react": "16.11.0",
"react-dom": "16.11.0",
"react-native": "https://github.com/expo/react-native/archive/sdk-38.0.2.tar.gz",
"react-native-gesture-handler": "~1.6.0",
"react-native-keyboard-aware-scroll-view": "^0.9.2",
"react-native-reanimated": "~1.9.0",
"react-native-safe-area-context": "~3.0.7",
"react-native-screens": "~2.9.0",
"react-native-web": "~0.11.7",
"react-navigation": "^3.11.1",
"react-navigation-header-buttons": "^3.0.1",
"react-redux": "^7.1.0",
"redux": "^4.0.4",
"redux-thunk": "^2.3.0"
},
"devDependencies": {
"babel-eslint": "^10.1.0",
"babel-preset-expo": "^8.2.3",
"eslint": "^7.10.0",
"eslint-config-airbnb": "^18.2.0",
"eslint-config-prettier": "^6.12.0",
"eslint-plugin-extra-rules": "0.0.0-development",
"eslint-plugin-import": "^2.22.0",
"eslint-plugin-jsx-a11y": "^6.3.1",
"eslint-plugin-prettier": "^3.1.4",
"eslint-plugin-react": "^7.21.2",
"eslint-plugin-react-native": "^3.9.1",
"eslint-plugin-sort-class-members": "^1.8.0",
"eslint-plugin-unused-imports": "^0.1.3",
"flow": "^0.2.3",
"flow-bin": "^0.134.0",
"prettier": "^2.1.2",
"redux-devtools-extension": "^2.13.8"
},
"private": true
}

package.json Working
```{
  "main": "node_modules/expo/AppEntry.js",
  "scripts": {
    "start": "expo start",
    "android": "expo start --android",
    "ios": "expo start --ios",
    "eject": "expo eject",
    "lint": "eslint . -c .eslintrc.js --ext .js",
    "flow": "flow",
    "publish-updates": "expo publish",
    "build-android-apk": "expo build:android -t apk",
    "build-android-aab": "expo build:android -t app-bundle",
    "build-ios": "expo build:ios"
  },
  "dependencies": {
    "@expo/vector-icons": "^10.2.1",
    "@react-native-community/masked-view": "0.1.5",
    "@react-navigation/drawer": "^5.0.0",
    "@react-navigation/native": "^5.0.0",
    "@react-navigation/stack": "^5.0.0",
    "expo": "^36.0.0",
    "expo-linear-gradient": "~8.0.0",
    "lodash": "^4.17.20",
    "moment": "^2.24.0",
    "prop-types": "^15.7.2",
    "react": "16.11.0",
    "react-dom": "16.9.0",
    "react-native": "https://github.com/expo/react-native/archive/sdk-36.0.1.tar.gz",
    "react-native-gesture-handler": "~1.5.0",
    "react-native-keyboard-aware-scroll-view": "^0.9.1",
    "react-native-reanimated": "~1.4.0",
    "react-native-safe-area-context": "0.6.0",
    "react-native-screens": "2.0.0-alpha.12",
    "react-native-web": "^0.11.7",
    "react-navigation": "^3.11.1",
    "react-navigation-header-buttons": "^3.0.1",
    "react-redux": "^7.1.0",
    "redux": "^4.0.4",
    "redux-thunk": "^2.3.0"
  },
  "devDependencies": {
    "babel-eslint": "^10.1.0",
    "babel-preset-expo": "^8.2.3",
    "eslint": "^7.10.0",
    "eslint-config-airbnb": "^18.2.0",
    "eslint-config-prettier": "^6.12.0",
    "eslint-plugin-extra-rules": "0.0.0-development",
    "eslint-plugin-import": "^2.22.0",
    "eslint-plugin-jsx-a11y": "^6.3.1",
    "eslint-plugin-prettier": "^3.1.4",
    "eslint-plugin-react": "^7.21.2",
    "eslint-plugin-react-native": "^3.9.1",
    "eslint-plugin-sort-class-members": "^1.8.0",
    "eslint-plugin-unused-imports": "^0.1.3",
    "flow": "^0.2.3",
    "flow-bin": "^0.134.0",
    "prettier": "^2.1.2",
    "redux-devtools-extension": "^2.13.8"
  },
  "private": true
}

try clearing your browser cache / using incognito

Same problem on Windows 10 with RN 0.62.2.
Not using expo.

Okay I just managed to fix this with Expo by installing the latest expo cli and using 'expo upgrade'.
Expo 39.0.3
Expo's React Native https://github.com/expo/react-native/archive/sdk-39.0.3.tar.gz

https://github.com/babel/minify/issues/950，
This solution helped me，Check your projects，in babel.config.js，'transform-remove-console'

@LixingY the link has an extra comma at the end, should be https://github.com/babel/minify/issues/950

Anyway, it didn't help me.

have you deleted this file transform-remove-console？then uninstall app and react-native start --reset-cache, then try it

发件人: Yossi notifications@github.com
发送时间: 2020年10月12日 10:11
收件人: facebook/react-native react-native@noreply.github.com
抄送: Aaron yanlixing@outlook.com; Mention mention@noreply.github.com
主题: Re: [facebook/react-native] Error: Unable to resolve module ./debugger-ui/debuggerWorker.cff11639.js from ``: (#28844)

@LixingYhttps://github.com/LixingY the link has an extra comma at the end, should be babel/minify#950https://github.com/babel/minify/issues/950

Anyway, it didn't help me.

―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/facebook/react-native/issues/28844#issuecomment-707025336, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJNF2S2W2FTL6ZDO2IS3FCLSKLI53ANCNFSM4M2TEMQQ.

I don't see this file in my tree.
One thing that I don't understand: the reference in babel is to production, and I am talking about debug mode.

If I set my device date to the future, then it won't perform any network request.

Well, i'm using react-native 0.63.3.
What i'm done to fix this is close all running program. Restart my OS and it's gone.
I think this happen when we let the program run and close the Lid or sleep for some long times.

Well, i'm using react-native 0.63.3.
What i'm done to fix this is close all running program. Restart my OS and it's gone.
I think this happen when we let the program run and close the Lid or sleep for some long times.

Doesn't work in my case (0.62.2)

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

Not relevant for me. I am not using react-navigation at all (and not expo, for other comments).

I reinstalled the Expo application, and the problem disappeared. Maybe it will help someone, too.

I have the same issue. Struggling with this for a few days :/
Can't debug my code.

same issue with "react-native": "0.62.2"
it disappears if i press cmd+R two times fast, but the next reload throws an error again

I got the error when I used 0.62.2. Just upgraded to 0.63.3 and the error is still there.

Not sure if this will help, but when I get in the metro bundler window the following:

The chrome console displays the following:

@rahamin1 Did you find babel.config.js file in your project ？

Did you find babel.config.js file in your project ？

Yes.

Its contents were:

module.exports = {
  presets: ['module:metro-react-native-babel-preset'],
};

I modified it per advise of somebody to:

module.exports = function(api) {
  api.cache(true);
  if (process.env.NODE_ENV === 'production' || process.env.BABEL_ENV === 'production') {
    return {
      "presets": ["module:metro-react-native-babel-preset"],
      "plugins": ["react-native-paper/babel", ["transform-remove-console", {"exclude": ["error", "warn", "info"]}]]
    }
  } else {
    return {
      "presets": ["module:metro-react-native-babel-preset"],
    }
  }
}

None of these helped.

@rahamin1 ok.. delete this code transform-remove-console,then close terminal, uninstall your app,close browser,then terminal execution yarn start --reset-cache

So you want the file to be the following?

module.exports = function(api) {
  api.cache(true);
  if (process.env.NODE_ENV === 'production' || process.env.BABEL_ENV === 'production') {
    return {
      "presets": ["module:metro-react-native-babel-preset"],
    }
  } else {
    return {
      "presets": ["module:metro-react-native-babel-preset"],
    }
  }
}

It is almost as it has been before, just adding api.cache(true)

@rahamin1 yeah, that's it, then close the browser terminal where you are running, uninstall the app of the simulator, then get into your project, yarn start --reset-cache, clear react-native run cache, that's what I did, the error goes away

That did the trick, but only once... OR maybe I missed the errors... Not sure anymore.
Then I tried again, and although I repeated the same steps, it doesn't work anymore...

Thanks for the help!

@rahamin1, maybe or you can delete api.cache(true) ?

In this case, I get my original file...
Although it didn't work, I appreciate your help!

In this case, I get my original file...
Although it didn't work, I appreciate your help!

Do you have console errors? Updating react-navigation resolved this issue for me.

Some warnings. No error.

Great to see a fix has been merged here, thanks for the work here. Do we have any idea when this would go live so we can use it?

I'm currently in the process of upgrading from Expo 37 —> 39, and this issue is preventing any debugging work, I guess the Expo guys would need to implement any fixes you put out. I've spent about 6 hours trying to find fixes for this, so if anyone knows a short-term solution other than rolling back to 37 let us know.

@fredrivett - hi there! i work on expo and so does @satya164, who fixed the issue. we're hoping to have a release backported to older rn-cli versions, but i'm not sure what timeline there is for that on the rn-cli side of things. @thymikee may be able to answer that better.

Thanks for the update @brentvatne, really appreciate all the work the Expo and React Native teams put in, makes our job as app developers so much easier. Thanks for doing what you can here.

Short term soultion should be to open debugger panel and clear cache.

Hmm, I still get the same error after clicking Clear site data there. I did that for both the Expo Developer Tools tab, and the React Native Debugger tab. I also have the latest version of React Native Debugger installed (0.11.5). I might have done a silly somewhere, I upgraded directly from Expo 37 —> 39. The exact error I'm getting is:

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

None of these files exist:
  * debugger-ui/debuggerWorker.cff11639.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|.native.svg|.svg)
  * debugger-ui/debuggerWorker.cff11639.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|.native.svg|.svg)
    at ModuleResolver.resolveDependency ([redacted]/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:163:15)
    at ResolutionRequest.resolveDependency ([redacted]/metro/src/node-haste/DependencyGraph/ResolutionRequest.js:52:18)
    at DependencyGraph.resolveDependency ([redacted]/node_modules/metro/src/node-haste/DependencyGraph.js:287:16)
    at [redacted]/node_modules/metro/src/lib/transformHelpers.js:267:42
    at Server.<anonymous> ([redacted]/node_modules/metro/src/Server.js:841:41)
    at Generator.next (<anonymous>)
    at asyncGeneratorStep ([redacted]/node_modules/metro/src/Server.js:99:24)
    at _next ([redacted]/node_modules/metro/src/Server.js:119:9)

Also try clearing Metro bundler cache: expo start -c

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

Fixed.

Please upgrade CLI to 4.13.1 as per this official React Native CLI guide.

Note this only works on React Native 0.62 and newer. No plans for backwards fixes for older versions.

• I am on Windows 10, running on an android emulator (genymotion).
• I removed node_modules, ran yarn install.
• Still getting:

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

None of these files exist:
  * debugger-ui\debuggerWorker.cff11639(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
  * debugger-ui\debuggerWorker.cff11639\index(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)

• Output from yarn list --pattern @react-native-community/cli:

yarn list v1.19.1
├─ @react-native-community/[email protected]
├─ @react-native-community/[email protected]
├─ @react-native-community/[email protected]
├─ @react-native-community/[email protected]
├─ @react-native-community/[email protected]
│  └─ @react-native-community/[email protected]
├─ @react-native-community/[email protected]
├─ @react-native-community/[email protected]
└─ @react-native-community/[email protected]
   └─ @react-native-community/[email protected]

@rahamin1 have you tried @satya164's instructions? https://github.com/facebook/react-native/issues/28844#issuecomment-728233645 and https://github.com/facebook/react-native/issues/28844#issuecomment-728459236

@thymikee I've tried all of the above and it didn't help.

@thymikee

@rahamin1 have you tried @satya164's instructions? #28844 (comment) and #28844 (comment)

Tried now. Didn't help.

I had a bug with Mobx. After solving this error, my problem (Error: Unable to resolve module ./debugger-ui/debuggerWorker) was solved.

Fixed.

Please upgrade CLI to 4.13.1 as per this official React Native CLI guide.

Note this only works on React Native 0.62 and newer. No plans for backwards fixes for older versions.

not working on 0.62.2

@kadiryaka said:

I had a bug with Mobx. After solving this error, my problem (Error: Unable to resolve module ./debugger-ui/debuggerWorker) was solved.

I'm wondering if my issue may be related to Mobx as well as I haven't had much luck with the solutions here-- could you share any insight into your Mobx issue?

You have to remove globally installed react-native-cli and use npx.

1. npm uninstall -g react-native
2. Find all the @react-native-community/cli prefixed entries in your project's lock file (package-lock or yarn.lock) and remove them
3. Reinstall node_modules : yarn install / npm install
4. Run your app with npx : npx react-native run-android

Didn't seem to help in my case: https://github.com/facebook/react-native/issues/28844#issuecomment-730535093

Didn't seem to help in my case: #28844 (comment)

Maybe try to also remove the app from device / emulator. I have this issue every once in a while and removing the app solves it (temporarily)

Another thing to add, this issue is doing nothing on iOS by my side but when running for Android the app behaves completely wrong

Thanks, but tried several times.

I analyze the app and device info and find my error reason. my device's time fast the actual time, after I set the device time as automatic the problem disappear.

Have exact same issue, I removed *.lock and node_modules and reinstalled all.
I am on "react-native": "0.63.4", and react-native-community/cli 4.13.1
Yet in the majority of times when trying to reload a project with the debugger on, it crashes (on real device and emulator) :(