Skip to content

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

@IvanGoranov02

Description

@IvanGoranov02

Website or app

Error

Repro steps

Cannot see

How often does this bug happen?

Every time

DevTools package (automated)

react-devtools-extensions

DevTools version (automated)

6.1.1-44c3d3d665

Error message (automated)

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

Error call stack (automated)

at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1192232
    at v.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1160378)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1161985
    at bridgeListener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1572692)

Error component stack (automated)


GitHub query string (automated)

https://github.com/api/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

Activity

JOBAYERAHAMED00

JOBAYERAHAMED00 commented on Apr 14, 2025

@JOBAYERAHAMED00

at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1192232
at v.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1160378)
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1161985
at bridgeListener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1572692)

csalazarPD

csalazarPD commented on Apr 15, 2025

@csalazarPD

same here! its happening

vegerot

vegerot commented on Apr 15, 2025

@vegerot

+1 This started happening to me today.

LennyLouis

LennyLouis commented on Apr 16, 2025

@LennyLouis

just happened now

pranavmappoli

pranavmappoli commented on Apr 18, 2025

@pranavmappoli

Any updates ?

rootlinux2

rootlinux2 commented on Apr 23, 2025

@rootlinux2

Same issue here!

The error was thrown at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1192232 at v.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1160378) at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1161985 at bridgeListener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1572692)

aalexgabi

aalexgabi commented on May 1, 2025

@aalexgabi

Also running into this with "restart and profile" feature.

zwift-mark

zwift-mark commented on May 3, 2025

@zwift-mark

same

lucho20pt

lucho20pt commented on May 5, 2025

@lucho20pt

I ran into an error message, Cannot add node "1" because a node with that id is already in the Store, specifically when trying to use the "Reload and start profiling" feature in React DevTools while on dynamic board page (app/(kanban)/board/[id]/page.tsx).

At first, I thought it might be because i was setting an HTML id attribute inside (components/kanban/list/list-card.tsx) which could potentially lead to duplicates if multiple lists had the same ID.

However, i found this GitHub issue where others reported the exact same error with the DevTools profiler, suggesting it's likely a bug within the DevTools extension itself.

Fix

Interestingly, i managed to fix it by switching my development command from next dev --turbopack to next dev, and then switching back.
Even after i put the HTML id back again (just to test if it was causing the issue), the profiler kept working.

This suggests the real fix was toggling the dev server, which probably cleared some temporary cache or state that was causing the conflict between Turbopack and the DevTools profiler.

So, it looks like it was a temporary tooling glitch rather than a bug in my code!

janvorwerk

janvorwerk commented on Jun 6, 2025

@janvorwerk

For me, switching off reactStrictMode was enough to avoid these issues

-- edit => unfortunately this came back even with strict mode turned off! 😭

milan-lakhani

milan-lakhani commented on Jun 11, 2025

@milan-lakhani

I Just had this issue right now :(

AstralHunt

AstralHunt commented on Jun 14, 2025

@AstralHunt

Issue also occurs for no apparent reason

shreyanshxyz

shreyanshxyz commented on Jun 23, 2025

@shreyanshxyz

so no fix as of yet ?

devAbreu

devAbreu commented on Jun 25, 2025

@devAbreu

My problem was that I had the same extension installed twice. I don't know why, I don't remember if I installed one from Chrome and one from Edge. I uninstalled both, and then left only one installed. And I haven't seen this problem again.

rootlinux2

rootlinux2 commented on Jul 21, 2025

@rootlinux2

I just got this issue:

Uncaught Error: Cannot add node "13" because a node with that id is already in the Store.
Dismiss
The error was thrown at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1236392
at v.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1203447)
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1205054
at bridgeListener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1620565)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @aalexgabi@vegerot@lucho20pt@rootlinux2@pranavmappoli

        Issue actions

          [DevTools Bug] Cannot add node "909" because a node with that id is already in the Store. · Issue #32852 · facebook/react