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

[samkhatri]

Website or app

https://wayray.com/#how-we-work

Repro steps

not able to see

How often does this bug happen?

Sometimes

DevTools package (automated)

react-devtools-extensions

DevTools version (automated)

4.19.2-20ca9b565

Error message (automated)

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

Error call stack (automated)

at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:25708:41
    at bridge_Bridge.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:23923:22)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:24083:12
    at listener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:52511:39)

Error component stack (automated)

No response

GitHub query string (automated)

https://api.github.com/search/issues?q=Cannot add node  because a node with that id is already in the Store. in:title is:issue is:open is:public label:"Component: Developer Tools" repo:facebook/react

[jstejada]

@samkhatri do you have multiple versions of the extension installed by any chance?

[MrJoy]

I have 4.20.0 installed, and just ran into the same problem. It was working fine, and then... boom. Not sure precisely when it happened -- I was editing code to resolve some errors, then when I went back to try things out in my app... It was in this state.

[jstejada]

@MrJoy, a couple of clarifying questions:

• have you seen this happen before v4.20.0?
• do you have multiple versions of the extension installed by any chance?

[peculiarity]

Extension verison: 4.20.0 (10/15/2021)

Haven't seen this issue before.
Today I wanted to investigate something and it turned out that I couldn't because the extension failed with the very same error.

[jstejada]

@peculiarity, same question for you, do you have multiple versions of the extension installed by any chance?

[jstejada]

also, @MrJoy, @peculiarity, @samkhatri, are you able to reproduce this issue 100% of the time? do you have any specific repro steps to reproduce it, or a small codesandbox or app where it can be reproduced?

[jstejada]

Looks like this might be a duplicate of #21636 (see this comment), and it has been reported several times in the past as well.

Which makes me think this is not a new issue introduced by v4.20, and is likely a long standing issue. Since it's hard to reproduce and likely due to a race condition it makes it hard to track down.

We'll continue to look into this if we can get a reliable repro case (and if you can provide one that would be super helpful).

In the meantime I'll merge this into #21636 and mark this as a duplicate.

[MrJoy]

@jstejada I do not have multiple versions of the extension installed, and I have never observed it before. That said, I don't use the extension often because I generally don't prefer to use Chrome. In my case it was a one-off that has yet to come up again.

[MrJoy]

Only other note of potential relevance: When it showed up, my un-ejected CRA app had compile errors and so my code wasn't actually running -- it was just rendering the development-mode error dump.