-
Notifications
You must be signed in to change notification settings - Fork 49k
Open
Labels
Component: Developer ToolsStatus: UnconfirmedA potential issue that we haven't yet confirmed as a bugA potential issue that we haven't yet confirmed as a bugType: Bug
Description
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
vegerot, amaletski, pranavmappoli, stefanoverna, richardasymmetric and 12 moreoimarcuseduardo and caocchinh
Metadata
Metadata
Assignees
Labels
Component: Developer ToolsStatus: UnconfirmedA potential issue that we haven't yet confirmed as a bugA potential issue that we haven't yet confirmed as a bugType: Bug
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
JOBAYERAHAMED00 commentedon Apr 14, 2025
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 commentedon Apr 15, 2025
same here! its happening
vegerot commentedon Apr 15, 2025
+1 This started happening to me today.
LennyLouis commentedon Apr 16, 2025
just happened now
pranavmappoli commentedon Apr 18, 2025
Any updates ?
rootlinux2 commentedon Apr 23, 2025
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 commentedon May 1, 2025
Also running into this with "restart and profile" feature.
zwift-mark commentedon May 3, 2025
same
lucho20pt commentedon May 5, 2025
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
tonext 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 commentedon Jun 6, 2025
For me, switching off reactStrictMode was enough to avoid these issues
-- edit => unfortunately this came back even with strict mode turned off! 😭
milan-lakhani commentedon Jun 11, 2025
I Just had this issue right now :(
AstralHunt commentedon Jun 14, 2025
Issue also occurs for no apparent reason
shreyanshxyz commentedon Jun 23, 2025
so no fix as of yet ?
devAbreu commentedon Jun 25, 2025
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 commentedon Jul 21, 2025
I just got this issue: