react-native-debugger: Cannot add node "1" because a node with that id is already in the Store.
React Native Debugger app version: 0.12.1 React Native version: 0.66.4 Platform: Android + iOS Is real device of platform: Android real device, iOS simulator Operating System: macOS
Steps to reproduce:
- Create new React Native project
npx react-native init rnapp - Start React Native Debugger
- Enable debugging in app
- Observe crash
Uncaught Error: Cannot add node "1" because a node with that id is already in the Store.
The error was thrown at /path/React Native Debugger.app/Contents/Resources/app.asar/node_modules/react-devtools-core/dist/standalone.js:48:140545
at c.emit (/path/React Native Debugger.app/Contents/Resources/app.asar/node_modules/react-devtools-core/dist/standalone.js:48:89515)
at /path/React Native Debugger.app/Contents/Resources/app.asar/node_modules/react-devtools-core/dist/standalone.js:48:90986
at /path/React Native Debugger.app/Contents/Resources/app.asar/node_modules/react-devtools-core/dist/standalone.js:48:347787
at Array.forEach (<anonymous>)
at S.Gc.e.onmessage (/path/React Native Debugger.app/Contents/Resources/app.asar/node_modules/react-devtools-core/dist/standalone.js:48:347771)
at S.n (/path/React Native Debugger.app/Contents/Resources/app.asar/node_modules/react-devtools-core/dist/standalone.js:40:3009)
at S.emit (events.js:315:20)
at e.exports.P (/path/React Native Debugger.app/Contents/Resources/app.asar/node_modules/react-devtools-core/dist/standalone.js:8:9318)
at e.exports.emit (events.js:315:20)
at e.exports.dataMessage (/path/React Native Debugger.app/Contents/Resources/app.asar/node_modules/react-devtools-core/dist/standalone.js:8:15409)
at e.exports.getData (/path/React Native Debugger.app/Contents/Resources/app.asar/node_modules/react-devtools-core/dist/standalone.js:8:14651)
at e.exports.startLoop (/path/React Native Debugger.app/Contents/Resources/app.asar/node_modules/react-devtools-core/dist/standalone.js:8:12066)
at e.exports._write (/path/React Native Debugger.app/Contents/Resources/app.asar/node_modules/react-devtools-core/dist/standalone.js:8:11421)
at doWrite (_stream_writable.js:403:12)
at writeOrBuffer (_stream_writable.js:387:5)
Related issues in https://github.com/facebook/react/:
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 45
- Comments: 22
Commits related to this issue
- Adding apollo Fixing react devtools not working properlyhttps://github.com/jhen0409/react-native-debugger/issues/668 — committed to fohtoh/hoopsdevelopment by stowelljr 2 years ago
Same issue on:
0.68.00.12.1Problem
The problem occurs due to
react-devtools-coreversion mismatch. React Native debugger uses"react-devtools-core": "4.14.0"(as of v0.12.0 changelog) butnpx react-native initcomes with the@latestversion.Remarks
When starting a project with
npx react-native init, it comes withreact-devtools-coreinstalled, notreact-devtools. Identify this withnpm listforeach of these packages (locally in your project, NOT global):So when it comes to
react-devtools-coredependency, notice that it is a nested dependency ofreact-native.As stated in https://docs.npmjs.com/cli/v8/configuring-npm/package-json#overrides, you are able to select different version for dependencies of your dependencies with the
overridesproperty inpackage.json. So the first thing that came in my mind, was adding the package version as an overrides topackage.jsonand running a cleannpm install:This will do the trick, but to be more precise
react-devtools-coreis a dependency ofreact-native, so it’s a dependency of your dependency as mentioned above.Solution
npx react-native init YourProjectName(if you haven’t already).node_modulesdirectory (andpackage-lock.jsonfile if any).react-devtools-coreanywhere in your dependencies & add these lines to yourpackage.json.Exact version depends on the ReactNativeDebugger’s current
react-devtools-coreversion (for0.12.0-0.12.1is4.14.0) Notice thatreact-devtools-coreis added as a dependency ofreact-native. 4. Runnpm install5. Uninstall any previous installs of your app, from you device or emulator 6. Now open React Native Debugger 7. Runnpm run android8. SelectingDebugfrom the developer menu, should now debug your app in ReactNativeDebuggerIMPORTANT NOTE: Not tested in macOS.
The same problem
Or in case you use yarn:
same issue v0.12.1
on Mac OS (M1) the following fixed it for me:
and, in the app’s
package.json:same issue here too
facing same issue
Facing the same issue too on pc This solution worked for me! https://github.com/facebook/react/issues/23226#issuecomment-1051006915
Facing same error. Any updates please?
same issue
I "npm install"ed (not globally) ‘react-devtools’ and ‘react-devtools-core’ and set them to the same version
“react-devtools”: “~4.14.0”, “react-devtools-core”: “~4.14.0”, and re-installed everything by deleting package-lock.json and node_modules
then ran npm install and it worked
I think the problem was those packages not being the same version
With React Native Debugger version 0.13.0 and a React Native project in 0.69.4, there is no need to add “overrides” or “resolution” for react-devtools-core in the package.json
Installing “'react-devtools” and “react-devtools-core” globally solved this issue by me. so just running:
In the react-devtools package, I got this all to work by upgrading both react-devtools and react-devtools-core to v4.22.1. If this repo could bump both versions up to put these packages back in sync that should hopefully solve the problem. Until then, I don’t think there’s a way to use this tool. I have the same error every time I launch, forcing me to go back to just plain react-devtools / browser-based react native debugger which launches with expo. It’s a real shame; I love how all of that is integrated in one place with RN-debugger.
For now, I just upgraded react-devtools from npm and customized the port it listens to via react-devtools-core, as documented here. Component and Profiler tabs, plus some console.logs is better than nothing I suppose!
“overrides” only works on npm version 8.3.0 and above. To update npm, run : npm install -g npm
same issue