[DevTools Bug] Cannot add child "1161" to parent "942" because parent node was not found in the Store.
Website or app
chrome on local host
Repro steps
it happen with every component that i mount

How often does this bug happen?
Every time
DevTools package (automated)
react-devtools-extensions
DevTools version (automated)
4.27.2-1a88fbb67
Error message (automated)
Cannot add child "1161" to parent "942" because parent node was not found in the Store.
Error call stack (automated)
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:27939:43
at bridge_Bridge.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:25892:22)
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:26061:14
at listener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:56323:39)
Error component stack (automated)
No response
GitHub query string (automated)
https://api.github.com/search/issues?q=Cannot add child to parent because parent node was not found in the Store. in:title is:issue is:open is:public label:"Component: Developer Tools" repo:facebook/react
@bhanuUdai
Can you please provide an example of the code that reproduces the problem? Some useful tips on this: https://stackoverflow.com/help/mcve
this error is coming with every react application i try to run on browser
On Mon, Apr 3, 2023 at 4:22 PM Ruslan Lesiutin @.***> wrote:
@bhanuUdai https://github.com/bhanuUdai
Can you please provide an example of the code that reproduces the problem? Some useful tips on this: https://stackoverflow.com/help/mcve
— Reply to this email directly, view it on GitHub https://github.com/facebook/react/issues/26465#issuecomment-1494099896, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2JXKJ6EIX5LUQWLKZKPCALW7KTW7ANCNFSM6AAAAAAWE2AJRY . You are receiving this because you were mentioned.Message ID: @.***>
Getting same along with Invalid renderer id "1". I regularly use React devtools but noticed this only today (which means it might've appeared within last ~1 week).
Another particularly different thing which happens is that Devtools Element tree becomes kind-of disconnected from real VDOM. i.e. hovering doesn't highlight corresponding element in window, neither I can inspect new elements.
This used to happen previously also (since ~3-4 months), and I could work around it by Pressing Option + R (reload devtools).
Now, when I try to reload devtools in such situation, I get warning Invalid renderer id "1" and devtools goes into above mentioned state.
And, service worker logs this as error message
{
"message": "Duplicate script ID 'hook'"
}
I have same issue.
I have same issue.
still running into the same problem as of september
I have same issue. (2024.03.27)
I have the same issue as the OP.
Uncaught Error: Cannot remove node "59709" because no matching node was found in the Store.
The error was thrown at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1193929
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)
I'm not sure if this is related to the issue, but I was able to resolve it by removing the fragment from the URL as follows:
- https://example.com/#page-1
+ https://example.com/
Uncaught Error: Cannot add child "36525" to parent "36117" because parent node was not found in the Store.
Dismiss
The error was thrown at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1227910
at v.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1195122)
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1196729
at bridgeListener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1607819)
If I have to guess, one of the components did not render because
reproducable in current latest next-js version
facing same issue on next-js v15.5.2 with zustand.
I'm not sure if this is related to the issue, but I was able to resolve it by removing the fragment from the URL as follows:
- https://example.com/#page-1
- https://example.com/
Thanks for the tip! Mine started working when I removed the query parameters from the URL
facing the same issues as well
Same issue.
same issue