Unable to resolve module ./debugger-ui/debuggerWorker.aca173c4.js #731

omar-bear · 2021-11-06T20:54:49Z

Report a bug
App crash when i turn debug on mode

versions

    "react-native": "0.66.0",
    "metro-react-native-babel-preset": "0.66.2",

What is the current behavior?
The app work fine but it crash when i turn it to debug mode

How can i reproduce the error?
After a yarn dev and yarn android when i turn it to debug mode it crash and i can see only the error below

You can test it by your self from here
install start-ui native

npx create-start-ui --native myApp

That will scaffold a new folder with the latest version of 🚀 Start UI [native] 🎉

Then just go to the created folder cd myApp and follow the Installation Guide.

What is the error I'm getting?
After a yarn dev and yarn android when i turn it to debug mode it crash and i can see only this error

Error: Unable to resolve module ./debugger-ui/debuggerWorker.aca173c4.js from /home/omar/Documents/Projects/JawDay-mobile/.: 

None of these files exist:
  * debugger-ui/debuggerWorker.aca173c4.js(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
  * debugger-ui/debuggerWorker.aca173c4.js/index(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
    at ModuleResolver.resolveDependency (/home/omar/Documents/Projects/JawDay-mobile/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:107:15)
    at DependencyGraph.resolveDependency (/home/omar/Documents/Projects/JawDay-mobile/node_modules/metro/src/node-haste/DependencyGraph.js:288:43)
    at /home/omar/Documents/Projects/JawDay-mobile/node_modules/metro/src/lib/transformHelpers.js:129:24
    at Server._resolveRelativePath (/home/omar/Documents/Projects/JawDay-mobile/node_modules/metro/src/Server.js:1072:12)
    at async Server.requestProcessor [as _processSourceMapRequest] (/home/omar/Documents/Projects/JawDay-mobile/node_modules/metro/src/Server.js:428:37)
    at async Server._processRequest (/home/omar/Documents/Projects/JawDay-mobile/node_modules/metro/src/Server.js:389:7)
Error: Unable to resolve module ./debugger-ui/debuggerWorker.aca173c4.js from /home/omar/Documents/Projects/JawDay-mobile/.: 

None of these files exist:
  * debugger-ui/debuggerWorker.aca173c4.js(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
  * debugger-ui/debuggerWorker.aca173c4.js/index(.native|.native.js|.js|.native.json|.json|.native.ts|.ts|.native.tsx|.tsx)
    at ModuleResolver.resolveDependency (/home/omar/Documents/Projects/JawDay-mobile/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:107:15)
    at DependencyGraph.resolveDependency (/home/omar/Documents/Projects/JawDay-mobile/node_modules/metro/src/node-haste/DependencyGraph.js:288:43)
    at /home/omar/Documents/Projects/JawDay-mobile/node_modules/metro/src/lib/transformHelpers.js:129:24
    at Server._resolveRelativePath (/home/omar/Documents/Projects/JawDay-mobile/node_modules/metro/src/Server.js:1072:12)
    at async Server.requestProcessor [as _processSourceMapRequest] (/home/omar/Documents/Projects/JawDay-mobile/node_modules/metro/src/Server.js:428:37)
    at async Server._processRequest (/home/omar/Documents/Projects/JawDay-mobile/node_modules/metro/src/Server.js:389:7)

this error guide me to metro modules so this is i put the issue here

what is metro config in the project
in file metro.config.js

/**
 * Metro configuration for React Native
 * https://github.com/facebook/react-native
 *
 */

module.exports = {
  transformer: {
    getTransformOptions: async () => ({
      transform: {
        experimentalImportSupport: false,
        inlineRequires: false, // false because of hermes issue https://github.com/storybookjs/react-native/issues/152
      },
    }),
  },
};

Can someone find solution for this probleme i tested all solutions here but it doesnt work

The text was updated successfully, but these errors were encountered:

motiz88 · 2021-11-10T21:20:33Z

@omar-bear Can you check which version of @react-native-community/cli-debugger-ui you have installed? It seems like react-native-community/cli#1307 should have fixed this.

Also, have you tried clearing your Chrome cache?

sayurimizuguchi · 2021-11-25T15:48:41Z

Deleting the Cache from Google Chrome fixed this issue for me.

Settings -> More Tools -> Clear browsing data

Make sure to select "All time"

exzos28 · 2021-11-25T18:19:57Z

Deleting the Cache from Google Chrome fixed this issue for me.

Settings -> More Tools -> Clear browsing data

Make sure to select "All time"

I open debugger in incognito and it doesn't work for me.

ahmedu007 · 2021-12-22T13:44:03Z

Failing for us too. Clearing the cache or anything else doesn't do anything. Any sort of help would be highly appreciated 🙏

PhilippLeh21 · 2021-12-29T14:17:13Z

I am building an app with react-native (without expo) and it works both on simulator and on actual iPhone. But when I go in debug mode (Shake and Debug with Chrome) on simulator, the screens turns black. In my opinion the app is still running, because I get the same error messages as before but I can't do anything.
All of the dependencies are up to date and reset of entire project doesn't help either. Does anyone experience the same issues and is there any fix?

claudineibr · 2021-12-31T14:32:18Z

Same problem here, I've tried everything and it didn't work I formatted my machine and nothing, the worst thing is that I'm in the final stage of the project and late.

motiz88 · 2021-12-31T17:24:23Z

Can someone who's experiencing this issue provide a minimal repro case for me to look at? Ideally as a GitHub repo plus step-by-step instructions (that include clearing Chrome's cache and restarting the debug session).

omar-bear · 2021-12-31T17:26:58Z

Can someone who's experiencing this issue provide a minimal repro case for me to look at? Ideally as a GitHub repo plus step-by-step instructions (that include clearing Chrome's cache and restarting the debug session).

You can install the project in the issue description and debug it directly, thanks ☺️

PhilippLeh21 · 2022-01-01T16:46:46Z

Since version 2.x of react-native-reanimated does not yet support remote debugging (https://docs.swmansion.com/react-native-reanimated/docs/#known-problems-and-limitations), I downgraded to Version 1.13.1. and the debugger finally worked again. Unfortunately I do not know yet, if the lower version of react-native-reanimated has any impact on other libraries which rely on it (react-navigation for example). I hope this helps a little. :)

poojaSivakumar97 · 2022-01-19T17:27:49Z

am facing same issue with "react-native":"0.65.2"

app works fine ,but crashes in debug mode

joshrizzo · 2022-01-19T21:15:47Z

Same issue here. At the very least, it needs to throw a better error than this. Our packages are:

    "@react-native-community/blur": "^3.6.0",
    "@react-native-masked-view/masked-view": "^0.2.6",
    "@react-navigation/bottom-tabs": "^6.0.9",
    "@react-navigation/native": "^6.0.6",
    "@react-navigation/stack": "^6.0.11",
    "fastestsmallesttextencoderdecoder": "^1.0.22",
    "joi": "^17.5.0",
    "moment": "^2.29.1",
    "react": "17.0.2",
    "react-error-boundary": "^3.1.4",
    "react-native": "0.66.3",
    "react-native-app-auth": "^6.4.0",
    "react-native-gesture-handler": "^1.10.3",
    "react-native-iap": "^7.5.1",
    "react-native-keychain": "^8.0.0",
    "react-native-linear-gradient": "^2.5.6",
    "react-native-markdown-display": "^7.0.0-alpha.2",
    "react-native-orientation-locker": "^1.4.0",
    "react-native-pager-view": "^5.4.9",
    "react-native-reanimated": "^2.3.0",
    "react-native-redash": "^16.2.3",
    "react-native-safe-area-context": "^3.3.2",
    "react-native-screens": "^3.10.1",
    "react-native-shared-element": "^0.8.3",
    "react-native-svg": "^12.1.1",
    "react-native-url-polyfill": "^1.3.0",
    "react-native-vector-icons": "^8.1.0",
    "react-native-video": "^5.2.0",
    "react-native-webview": "^11.16.0",
    "react-navigation-shared-element": "^3.1.3",
    "react-query": "3.24.4"

vyshakh · 2022-01-31T07:55:06Z

I had similar issue, and I found out that react-native-reanimated package caused the issue for me.
Please note that Reanimated 2 doesn't support remote debugging, only Flipper can be used for debugging.
https://docs.swmansion.com/react-native-reanimated/docs/fundamentals/installation/

danpettay · 2022-02-02T04:43:23Z

I am experiencing this same error although am not using metro-react-native-babel-preset, just metro. What I've found is booting up a brand new expo project (SDK 44, comes with metro 0.64) and upgrading to metro 0.65.2 causes the debugger issue, and downgrading back to 0.64 resolves it

Rubon72 · 2022-02-13T10:33:57Z

I had similar issue, and I found out that react-native-reanimated package caused the issue for me. Please note that Reanimated 2 doesn't support remote debugging, only Flipper can be used for debugging. https://docs.swmansion.com/react-native-reanimated/docs/fundamentals/installation/

how to debug webSocket in flipper?

mukash · 2022-03-07T06:08:42Z

The issue still persist in "react-native": "0.67.2"
any help here?

edritech93 · 2022-03-22T05:12:31Z

same issue for me

sionel · 2022-03-24T09:00:24Z

Do you use "react-native-performance"?

lid3rs · 2022-04-11T16:06:30Z

Installing @react-native-community/cli-debugger-ui + clearing application data in inspect solved this to me.

omar-bear · 2022-04-18T13:52:30Z

Fixed for me with upgrade react-native-reanimated to 2.7.0

jkohlin · 2022-04-25T19:11:34Z

@react-native-community/cli-debugger-ui

This is not helping for me I'm afraid 😟
It started after I built the app to an iPhone.
Could it be react-native-iap? that's the only thing I installed recently.

AndersonVanzo · 2022-04-26T18:24:19Z

I've spend two days trying to solve this problem, but couldn't find any solution, so what I'm doing now is debug the app with Flipper, I don't like as much debug with Chrome but is the only solution I have found

g-nogueira · 2022-05-11T20:21:21Z

Installing @react-native-community/cli-debugger-ui + clearing application data in inspect solved this to me.

This worked for me. I did both the install and clearing the Expo data + cache in the phone.

esadkrs · 2022-05-20T12:17:18Z

Expo build app doesn't crash but still log the same error for me when debugger is on:

Error: Unable to resolve module ./debugger-ui/debuggerWorker.aca173c4

jucoba · 2022-05-21T13:14:37Z

same issue, Error: Unable to resolve module ./debugger-ui/debuggerWorker.aca173c4.
Worked for me to uninstall Expo from Android, run expo start again, open on android, it install expo again on my device and then in worked.

FatmaMahmoud698 · 2022-05-30T12:54:31Z

I face the error when I enable debug mode on the expo app

FatmaMahmoud698 · 2022-05-30T13:14:25Z

@lid3rs
I tried your step but still the same problem

TkhiienLok · 2022-06-07T08:49:39Z

I am on macOS, I installed React Native Debugger brew install react-native-debugger as it was adviced in corresponding section in the expo documentation https://docs.expo.dev/workflow/debugging/ , and the error was gone, so I was able to debug the app in vscode

robin3317 · 2022-07-01T02:22:43Z

I've spend two days trying to solve this problem, but couldn't find any solution, so what I'm doing now is debug the app with Flipper, I don't like as much debug with Chrome but is the only solution I have found

WEIRD but true! I try to connect my app with flipper, it fails to connect but solve my issue. Still shows the same error in terminal but debugger is running on chrome devtool smoothly!

agrittiwari · 2022-07-06T10:54:50Z

Error in debuuger console

Error: Requiring module "node_modules\react-native-reanimated\src\Animated.js", which threw an exception: Invariant Violation: Calling synchronous methods on native modules is not supported in Chrome.

 Consider providing alternative methods to expose this method in debug mode, e.g. by exposing constants ahead-of-time.

And the reanimated package version "react-native-reanimated": "~2.8.0", with autoupdates doesn't support the remote debugging, Flipper is the only option for now

As the library uses JSI for synchronous native methods access, remote debugging is no longer possible. You can use Flipper for debugging your JS code, however connecting debugger to JS context which runs on the UI thread is not currently supported.
Read

@PhilippLeh21 Thanks 🎩

msgadi · 2022-08-17T09:24:43Z

I am also facing the same issue. App runs fine but unable to debug. Getting same error. Tried all solution mentioned here.

KrushnaNaghate · 2022-08-27T13:21:15Z

I visited this page 2 and a half months ago and tried npm i @react-native-community/cli-debugger-ui from someone's answer, this does not work for me,

MichelBahl · 2022-09-12T17:43:20Z

For testing and using debugger I temporarily downgrade react-native-reanimated to "react-native-reanimated": "~2.3.0"
and delete watchman cache watchman watch-del-all

Gafum · 2022-11-16T15:07:55Z

I cleared the cache of the expo app on the phone and it helped.

rossnoble · 2022-11-23T15:29:08Z

I've often run into this issue when I have a bad import or some other kind of type error that breaks the build. The app and the web debugger will usually boot, but the app gets hung on the loading screen and the metro log error is displayed. It can sometimes be a PITA to hunt down the issue, so it helps to run a typecheck to find the offending file.

Can't guarantee this applies to all cases mentioned in this thread, but worth a try if you're stuck.

pawan9124 · 2022-11-23T16:03:21Z

This error start for me after I start debugging remotely in emulator ios, using command shift+m, toggle developer menu >enabled Debug Remote JS. Although disabling debug remote js helps to evade the error for now. But still looking for complete solution.

Lucas-191435 · 2022-12-27T18:03:26Z

turn off the debugger ,
exit the debugger ,

desligue o debugger ,
saia do debugger ,

cr7cr8 · 2023-02-14T06:27:12Z

Unable to resolve module ./debugger-ui/debuggerWorker.aca173c4.js

I fixed it by reinstalling the ExpoGo on my phone.

iamnabink · 2023-02-18T17:30:36Z

I am too getting this exact issue Unable to resolve module ./debugger-ui/debuggerWorker.aca

"dependencies": { "expo": "~47.0.12", "react": "18.1.0", "react-native": "0.70.5" }

Any workaround? or should I just ignore this?

ZexinW · 2023-02-20T02:52:21Z

same issue for me

MyTrainings2020 · 2023-02-22T03:52:25Z

After trying so many things mentioned above (with no fix), finally I did find the solution my own, go to your phone's app settings choose (expo go) app, i- Remove Cache ii- Remove App Data. restart the expo app on the phone.

run the server again (npm start or expo start)

it should work perfectly fine.

robhogan · 2023-02-22T09:56:28Z

It seems like folks are still encountering this issue frequently, and we’d like to do something about it. I haven’t been able to reproduce the problem though - if anyone who’s experiencing this could share as much detail as they can about their setup and sequence of events, ideally with a repro to clone, that’d be extremely helpful.

Harikarthyk · 2023-02-25T11:01:21Z

same issue for me.

When I stop Chrome debugging, the app works fine, but when I debug using Chrome, I get errors.

k88manish · 2023-03-18T17:18:08Z

It started happening for me when I upgraded my app to RN 0.71.

shashant19 · 2023-04-10T20:22:37Z

Adding getTransformOptions to metro config transformer fixed the issue for me (RN - 71.6)

`transformer: {

  getTransformOptions: async () => ({
    transform: {
      experimentalImportSupport: false,
      inlineRequires: true,
    },
  }),
  ...

}`

arnaudambro · 2023-04-21T12:54:57Z

found here: react-native-community/cli#1081 (comment)

manually uninstall the app
npm run start --reset-cache

done !

alex-mironov · 2023-05-01T22:09:00Z

adb reverse tcp:8081 tcp:8081 this is what helped me

httol · 2023-05-31T00:48:35Z

root reason maybe the who using react-native-reanimated library.

RmondJone · 2023-06-16T01:11:22Z

It's really frustrating, and it's been so long since this problem has not been solved. I read above that it was caused by the react-native-reanimation library, but there is no such library in my lock file.

Error info:

 BUNDLE  ./index.android.js

Error: Unable to resolve module ./debugger-ui/debuggerWorker.aca173c4 from D:\ZczyOverland\PluginReact/.:

None of these files exist:
  * debugger-ui\debuggerWorker.aca173c4(.native|.native.jsx|.jsx|.native.js|.js|.native.ts|.ts|.native.tsx|.tsx|.native.json|.json)
  * debugger-ui\debuggerWorker.aca173c4\index(.native|.native.jsx|.jsx|.native.js|.js|.native.ts|.ts|.native.tsx|.tsx|.native.json|.json)
    at ModuleResolver.resolveDependency (D:\ZczyOverland\PluginReact\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:107:15)
    at DependencyGraph.resolveDependency (D:\ZczyOverland\PluginReact\node_modules\metro\src\node-haste\DependencyGraph.js:288:43)
    at D:\ZczyOverland\PluginReact\node_modules\metro\src\lib\transformHelpers.js:129:24
    at Server._resolveRelativePath (D:\ZczyOverland\PluginReact\node_modules\metro\src\Server.js:1072:12)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at a

PS D:\ZczyOverland\PluginReact> npx react-native info
info Fetching system and libraries information...
System:
    OS: Windows 10 10.0.22621
    CPU: (16) x64 13th Gen Intel(R) Core(TM) i5-13400
    Memory: 5.94 GB / 15.70 GB
  Binaries:
    Node: 16.14.0 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 8.3.1 - C:\Program Files\nodejs\npm.CMD
    Watchman: Not Found
  SDKs:
    Android SDK: Not Found
    Windows SDK: Not Found
  IDEs:
    Android Studio: Version     2020.3.0.0 AI-203.7717.56.2031.7621141
    Visual Studio: Not Found
  Languages:
    Java: 11.0.18 - C:\Program Files\Common Files\Oracle\Java\javapath\javac.EXE
  npmPackages:
    @react-native-community/cli: 6.4.0 => 6.4.0
    react: 17.0.2 => 17.0.2
    react-native: 0.65.3 => 0.65.3
    react-native-windows: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

metro.config.js

/**
 * Metro configuration for React Native
 * https://github.com/facebook/react-native
 *
 * @format
 */

module.exports = {
  transformer: {
    getTransformOptions: async () => ({
      transform: {
        experimentalImportSupport: false,
        inlineRequires: true,
      },
    }),
  },
  resolver: {
    sourceExts: ['jsx', 'js', 'ts', 'tsx'],
  },
};

babel.config.js

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

package.json

  "dependencies": {
    "@react-navigation/bottom-tabs": "6.5.7",
    "@react-navigation/material-top-tabs": "6.6.2",
    "@react-navigation/native": "6.1.6",
    "@react-navigation/native-stack": "6.9.12",
    "date-fns": "2.30.0",
    "react": "17.0.2",
    "react-native": "0.65.3",
    "react-native-fast-image": "8.6.3",
    "react-native-gesture-handler": "2.9.0",
    "react-native-modal": "13.0.1",
    "react-native-pager-view": "6.0.1",
    "react-native-picker": "4.3.7",
    "react-native-safe-area-context": "4.5.1",
    "react-native-screens": "3.20.0",
    "react-native-tab-view": "3.5.1",
    "react-native-webview": "11.26.1",
    "rmc-date-picker": "6.0.10",
    "use-subscription": ">=1.0.0 <1.6.0",
    "react-freeze": "1.0.3",
    "zustand": "4.3.8"
  }，
  "devDependencies": {
    "@babel/core": "^7.12.9",
    "@babel/runtime": "^7.12.5",
    "@tsconfig/react-native": "2.0.3",
    "@types/react": "17.0.2",
    "@types/react-native": "0.65.3",
    "@react-native-community/cli": "6.4.0",
    "metro-react-native-babel-preset": "0.66.0",
    "prettier": "2.8.8",
    "typescript": "4.9.5"
  }

RmondJone · 2023-06-16T01:12:46Z

It's really frustrating, and it's been so long since this problem has not been solved. I read above that it was caused by the react-native-reanimation library, but there is no such library in my lock file.

Error info:

 BUNDLE  ./index.android.js

Error: Unable to resolve module ./debugger-ui/debuggerWorker.aca173c4 from D:\ZczyOverland\PluginReact/.:

None of these files exist:
  * debugger-ui\debuggerWorker.aca173c4(.native|.native.jsx|.jsx|.native.js|.js|.native.ts|.ts|.native.tsx|.tsx|.native.json|.json)
  * debugger-ui\debuggerWorker.aca173c4\index(.native|.native.jsx|.jsx|.native.js|.js|.native.ts|.ts|.native.tsx|.tsx|.native.json|.json)
    at ModuleResolver.resolveDependency (D:\ZczyOverland\PluginReact\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:107:15)
    at DependencyGraph.resolveDependency (D:\ZczyOverland\PluginReact\node_modules\metro\src\node-haste\DependencyGraph.js:288:43)
    at D:\ZczyOverland\PluginReact\node_modules\metro\src\lib\transformHelpers.js:129:24
    at Server._resolveRelativePath (D:\ZczyOverland\PluginReact\node_modules\metro\src\Server.js:1072:12)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at a

PS D:\ZczyOverland\PluginReact> npx react-native info
info Fetching system and libraries information...
System:
    OS: Windows 10 10.0.22621
    CPU: (16) x64 13th Gen Intel(R) Core(TM) i5-13400
    Memory: 5.94 GB / 15.70 GB
  Binaries:
    Node: 16.14.0 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 8.3.1 - C:\Program Files\nodejs\npm.CMD
    Watchman: Not Found
  SDKs:
    Android SDK: Not Found
    Windows SDK: Not Found
  IDEs:
    Android Studio: Version     2020.3.0.0 AI-203.7717.56.2031.7621141
    Visual Studio: Not Found
  Languages:
    Java: 11.0.18 - C:\Program Files\Common Files\Oracle\Java\javapath\javac.EXE
  npmPackages:
    @react-native-community/cli: 6.4.0 => 6.4.0
    react: 17.0.2 => 17.0.2
    react-native: 0.65.3 => 0.65.3
    react-native-windows: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

metro.config.js

/**
 * Metro configuration for React Native
 * https://github.com/facebook/react-native
 *
 * @format
 */

module.exports = {
  transformer: {
    getTransformOptions: async () => ({
      transform: {
        experimentalImportSupport: false,
        inlineRequires: true,
      },
    }),
  },
  resolver: {
    sourceExts: ['jsx', 'js', 'ts', 'tsx'],
  },
};

babel.config.js

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

package.json

  "dependencies": {
    "@react-navigation/bottom-tabs": "6.5.7",
    "@react-navigation/material-top-tabs": "6.6.2",
    "@react-navigation/native": "6.1.6",
    "@react-navigation/native-stack": "6.9.12",
    "date-fns": "2.30.0",
    "react": "17.0.2",
    "react-native": "0.65.3",
    "react-native-fast-image": "8.6.3",
    "react-native-gesture-handler": "2.9.0",
    "react-native-modal": "13.0.1",
    "react-native-pager-view": "6.0.1",
    "react-native-picker": "4.3.7",
    "react-native-safe-area-context": "4.5.1",
    "react-native-screens": "3.20.0",
    "react-native-tab-view": "3.5.1",
    "react-native-webview": "11.26.1",
    "rmc-date-picker": "6.0.10",
    "use-subscription": ">=1.0.0 <1.6.0",
    "react-freeze": "1.0.3",
    "zustand": "4.3.8"
  }，
  "devDependencies": {
    "@babel/core": "^7.12.9",
    "@babel/runtime": "^7.12.5",
    "@tsconfig/react-native": "2.0.3",
    "@types/react": "17.0.2",
    "@types/react-native": "0.65.3",
    "@react-native-community/cli": "6.4.0",
    "metro-react-native-babel-preset": "0.66.0",
    "prettier": "2.8.8",
    "typescript": "4.9.5"
  }

I hope to pay attention to this problem, because this should be the most basic function of the RN framework. If you can’t even use debug, then we really consider switching to Flutter. After all, Flutter doesn’t have these problems.

RmondJone · 2023-06-16T01:53:44Z

I guess it is the problem here. The code is ./debugger-ui/debuggerWorker, but the node_modules is cli-debugger-ui. I will verify it later. It is estimated that it has something to do with this

RmondJone · 2023-06-16T02:52:49Z

It still doesn’t work. Even if I change the path to the right one, it’s useless to find it. It’s a white screen when I enter

hileix · 2023-08-19T07:52:28Z

I have the same issue. But if I visit the debug URL: http://localhost:8081/debugger-ui/, it works for me, and then the error disappears.

IncrediblePony · 2023-09-26T15:02:15Z

I am on macOS, I installed React Native Debugger brew install react-native-debugger as it was adviced in corresponding section in the expo documentation https://docs.expo.dev/workflow/debugging/ , and the error was gone, so I was able to debug the app in vscode

I assume it is because the debugger looks for some sort of filesystem/files that would correspond with a debugger. When I open my emulator in debug mode with "just" the Firefox debugger this message "comes to life". When I open it with React Native Debugger it goes away. In and of itself the error message is pretty useless, and it creates unnecessary noise. It doesn't seem to crash or in other ways harm performance (more than usual at least).

Installing and running Flipper might work. Running the React Native Debugger extension for Chrome might work. Visiting the debugger ui URL as suggested by @hileix might also work

lazaro-contato · 2023-10-16T16:12:21Z

I tried many solutions about this and nothing works. For me the solution was to install Flipper (https://fbflipper.com/) and debug the entire project with it. For some reason React Native Debbugger doesn't work very well with React Reanimated.

kuldeepworkid · 2023-11-27T11:07:03Z

For me, it was working in real device but getting this error in simulator.
Im using React Native debugger.
I resolved it by following steps:

Run the app in real device and turn on the debug mode. (logs started showing in the debugger)
Now run the app in the simulator without debug mode.
Now turn on the debug mode in simulator.
Now the log will start showing in the debugger.

This comment has been minimized.

Sign in to view

This comment was marked as off-topic.

Sign in to view

yqrashawn mentioned this issue Nov 15, 2022

chore: fix can't remove node 0 error breaking react-devtools status-im/status-mobile#14316

Merged

Unable to resolve module ./debugger-ui/debuggerWorker.aca173c4.js #731

Unable to resolve module ./debugger-ui/debuggerWorker.aca173c4.js #731

Comments

omar-bear commented Nov 6, 2021 • edited

motiz88 commented Nov 10, 2021 • edited

This comment has been minimized.

sayurimizuguchi commented Nov 25, 2021 • edited

exzos28 commented Nov 25, 2021

ahmedu007 commented Dec 22, 2021

PhilippLeh21 commented Dec 29, 2021 • edited

claudineibr commented Dec 31, 2021

motiz88 commented Dec 31, 2021

omar-bear commented Dec 31, 2021

PhilippLeh21 commented Jan 1, 2022

poojaSivakumar97 commented Jan 19, 2022 • edited

joshrizzo commented Jan 19, 2022

vyshakh commented Jan 31, 2022

danpettay commented Feb 2, 2022

Rubon72 commented Feb 13, 2022

mukash commented Mar 7, 2022

edritech93 commented Mar 22, 2022

sionel commented Mar 24, 2022

lid3rs commented Apr 11, 2022

omar-bear commented Apr 18, 2022

jkohlin commented Apr 25, 2022

AndersonVanzo commented Apr 26, 2022

g-nogueira commented May 11, 2022

esadkrs commented May 20, 2022

jucoba commented May 21, 2022

FatmaMahmoud698 commented May 30, 2022

FatmaMahmoud698 commented May 30, 2022

This comment was marked as off-topic.

TkhiienLok commented Jun 7, 2022 • edited

robin3317 commented Jul 1, 2022

agrittiwari commented Jul 6, 2022 • edited

Error in debuuger console

msgadi commented Aug 17, 2022

KrushnaNaghate commented Aug 27, 2022

MichelBahl commented Sep 12, 2022

Gafum commented Nov 16, 2022 • edited

rossnoble commented Nov 23, 2022

pawan9124 commented Nov 23, 2022

Lucas-191435 commented Dec 27, 2022

turn off the debugger , exit the debugger ,

cr7cr8 commented Feb 14, 2023

iamnabink commented Feb 18, 2023

ZexinW commented Feb 20, 2023

MyTrainings2020 commented Feb 22, 2023

robhogan commented Feb 22, 2023

Harikarthyk commented Feb 25, 2023

k88manish commented Mar 18, 2023

shashant19 commented Apr 10, 2023 • edited

arnaudambro commented Apr 21, 2023

alex-mironov commented May 1, 2023

httol commented May 31, 2023

RmondJone commented Jun 16, 2023

RmondJone commented Jun 16, 2023

RmondJone commented Jun 16, 2023

RmondJone commented Jun 16, 2023

hileix commented Aug 19, 2023 • edited

IncrediblePony commented Sep 26, 2023

lazaro-contato commented Oct 16, 2023

kuldeepworkid commented Nov 27, 2023

omar-bear commented Nov 6, 2021 •

edited

motiz88 commented Nov 10, 2021 •

edited

sayurimizuguchi commented Nov 25, 2021 •

edited

PhilippLeh21 commented Dec 29, 2021 •

edited

poojaSivakumar97 commented Jan 19, 2022 •

edited

TkhiienLok commented Jun 7, 2022 •

edited

agrittiwari commented Jul 6, 2022 •

edited

Gafum commented Nov 16, 2022 •

edited

turn off the debugger ,
exit the debugger ,

shashant19 commented Apr 10, 2023 •

edited

hileix commented Aug 19, 2023 •

edited