Cannot add node "1" because a node with that id is already in the Store. #668

friederbluemle · 2021-12-15T14:01:52Z

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/:

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

TamaraMalakhova · 2021-12-28T09:38:17Z

The same problem

champagneht · 2021-12-30T08:57:14Z

The same problem

nanxiaobei · 2022-01-04T03:18:38Z

Same issue. version v0.12.1.

anhquan291 · 2022-01-08T09:31:50Z

Facing same error. Any updates please?

Slyness98 · 2022-01-11T19:13:13Z

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!

AdhamMoussa · 2022-01-29T14:03:50Z

same issue v0.12.1

Alaaa-Drebate · 2022-02-04T05:24:36Z

same issue here too

dkang23 · 2022-02-06T20:31:01Z

same issue

dkang23 · 2022-02-06T21:29:46Z

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!

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

nancologist · 2022-02-06T22:51:10Z

On Mac I could not even install react-devtools globally, because of electron. But it finally worked with following options:

sudo npm i -g react-devtools --unsafe-perm=true --allow-root=true

so as a work-around you can run react-devtools in Terminal and connect it to your virtual device

farukomer58 · 2022-02-15T14:23:21Z

Installing "'react-devtools" and "react-devtools-core" globally solved this issue by me.
so just running:

npm install -g react-devtools
npm install -g react-devtools-core

CaptainHaider · 2022-02-17T20:41:34Z

facing same issue

Alex1899 · 2022-02-20T13:40:17Z

same issue

JavaScriptErika · 2022-03-02T21:47:02Z

Facing the same issue too on pc
This solution worked for me! facebook/react#23226 (comment)

DreamEmulator · 2022-03-31T08:28:18Z

+1

musikobios · 2022-04-06T10:33:31Z

Same issue on:

Windows 10
ReactNative 0.68.0
ReactNative Debugger 0.12.1

Problem

The problem occurs due to react-devtools-core version mismatch.
React Native debugger uses "react-devtools-core": "4.14.0" (as of v0.12.0 changelog) but npx react-native init comes with the @latest version.

Remarks

When starting a project with npx react-native init, it comes with react-devtools-core installed, not react-devtools. Identify this with npm list foreach of these packages (locally in your project, NOT global):

So when it comes to react-devtools-core dependency, notice that it is a nested dependency of react-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 overrides property in package.json. So the first thing that came in my mind, was adding the package version as an overrides to package.json and running a clean npm install:

"overrides": {
    "react-devtools-core": "4.14.0"
}

This will do the trick, but to be more precise react-devtools-core is a dependency of react-native, so it's a dependency of your dependency as mentioned above.

Solution

Run npx react-native init YourProjectName (if you haven't already).
Delete node_modules directory (and package-lock.json file if any).
Be sure that you don't have react-devtools-core anywhere in your dependencies & add these lines to your package.json.

"overrides": {
    "react-native": {
        "react-devtools-core": "4.14.0"
    }
}

Exact version depends on the ReactNativeDebugger's current react-devtools-core version (for 0.12.0-0.12.1 is 4.14.0)
Notice that react-devtools-core is added as a dependency of react-native.
4. Run npm install
5. Uninstall any previous installs of your app, from you device or emulator
6. Now open React Native Debugger
7. Run npm run android
8. Selecting Debug from the developer menu, should now debug your app in ReactNativeDebugger

IMPORTANT NOTE: Not tested in macOS.

ThomasStubbe · 2022-04-07T14:32:37Z

Or in case you use yarn:

  "resolutions": {
    "react-devtools-core": "4.14.0"
  },

dudeinthemirror · 2022-04-27T21:16:34Z

on Mac OS (M1) the following fixed it for me:

yarn global add react-devtools react-devtools-core

and, in the app's package.json:

"resolutions": {
    "react-devtools-core": "4.14.0"
  },

Fixing react devtools not working properlyhttps://github.com/jhen0409/react-native-debugger/issues/668

pavelgronsky · 2022-05-11T09:27:42Z

Hey everyone!!!

This is my solution

samvoults · 2022-06-12T15:14:48Z

"overrides" only works on npm version 8.3.0 and above. To update npm, run : npm install -g npm

rossjackson · 2022-06-26T07:35:57Z

For those that don't want to use yarn #620 (comment)

Lunotte · 2022-08-17T11:49:34Z

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

prabhg mentioned this issue Feb 3, 2022

[DevTools Bug] Cannot add node "1" because a node with that id is already in the Store. facebook/react#23226

Open

fohtoh pushed a commit to fohtoh/hoopsdevelopment that referenced this issue May 5, 2022

Adding apollo

fcf72ab

Fixing react devtools not working properlyhttps://github.com/jhen0409/react-native-debugger/issues/668

maximveksler mentioned this issue May 15, 2022

[DevTools Bug] Cannot add node "1" because a node with that id is already in the Store. facebook/react#24437

Closed

DonRyu mentioned this issue Jul 3, 2022

Cannot add node "1" because a node with that id is already #708

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Cannot add node "1" because a node with that id is already in the Store. #668

Cannot add node "1" because a node with that id is already in the Store. #668

friederbluemle commented Dec 15, 2021 •

edited

Loading

TamaraMalakhova commented Dec 28, 2021

champagneht commented Dec 30, 2021

nanxiaobei commented Jan 4, 2022

anhquan291 commented Jan 8, 2022

Slyness98 commented Jan 11, 2022

AdhamMoussa commented Jan 29, 2022

Alaaa-Drebate commented Feb 4, 2022

dkang23 commented Feb 6, 2022

dkang23 commented Feb 6, 2022 •

edited

Loading

nancologist commented Feb 6, 2022

farukomer58 commented Feb 15, 2022

CaptainHaider commented Feb 17, 2022

Alex1899 commented Feb 20, 2022

JavaScriptErika commented Mar 2, 2022 •

edited

Loading

DreamEmulator commented Mar 31, 2022

musikobios commented Apr 6, 2022 •

edited

Loading

ThomasStubbe commented Apr 7, 2022

dudeinthemirror commented Apr 27, 2022

pavelgronsky commented May 11, 2022

samvoults commented Jun 12, 2022 •

edited

Loading

rossjackson commented Jun 26, 2022

Lunotte commented Aug 17, 2022

Cannot add node "1" because a node with that id is already in the Store. #668

Cannot add node "1" because a node with that id is already in the Store. #668

Comments

friederbluemle commented Dec 15, 2021 • edited Loading

TamaraMalakhova commented Dec 28, 2021

champagneht commented Dec 30, 2021

nanxiaobei commented Jan 4, 2022

anhquan291 commented Jan 8, 2022

Slyness98 commented Jan 11, 2022

AdhamMoussa commented Jan 29, 2022

Alaaa-Drebate commented Feb 4, 2022

dkang23 commented Feb 6, 2022

dkang23 commented Feb 6, 2022 • edited Loading

nancologist commented Feb 6, 2022

farukomer58 commented Feb 15, 2022

CaptainHaider commented Feb 17, 2022

Alex1899 commented Feb 20, 2022

JavaScriptErika commented Mar 2, 2022 • edited Loading

DreamEmulator commented Mar 31, 2022

musikobios commented Apr 6, 2022 • edited Loading

Problem

Remarks

Solution

ThomasStubbe commented Apr 7, 2022

dudeinthemirror commented Apr 27, 2022

pavelgronsky commented May 11, 2022

samvoults commented Jun 12, 2022 • edited Loading

rossjackson commented Jun 26, 2022

Lunotte commented Aug 17, 2022

friederbluemle commented Dec 15, 2021 •

edited

Loading

dkang23 commented Feb 6, 2022 •

edited

Loading

JavaScriptErika commented Mar 2, 2022 •

edited

Loading

musikobios commented Apr 6, 2022 •

edited

Loading

samvoults commented Jun 12, 2022 •

edited

Loading