react: [DevTools Bug] Cannot remove node "XX" because no matching node was found in the Store.
Website or app
Repro steps
Using next 12.3 and windows 10 chrome 108.0.5359.99 (Official Build) (64-bit)
- Open the inspector
- Navigate to the components tab. Open it a few times until it displays something. (blank screen issue already logged #22034 )
- eventually it will display the component tree, but after one scroll, it fails with this error:
Uncaught Error: Cannot remove node “1946” because no matching node was found in the Store. Dismiss The error was thrown at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:27994:43 at bridge_Bridge.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:25895:22) at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:26064:14 at listener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:56299:39)
How often does this bug happen?
Often
DevTools package (automated)
react-devtools-extensions
DevTools version (automated)
4.27.1-47f63dc54
Error message (automated)
Cannot remove node “1946” because no matching node was found in the Store.
Error call stack (automated)
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:27994:43
at bridge_Bridge.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:25895:22)
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:26064:14
at listener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:56299:39)
Error component stack (automated)
No response
GitHub query string (automated)
https://api.github.com/search/issues?q=Cannot remove node because no matching node was found in the Store. in:title is:issue is:open is:public label:"Component: Developer Tools" repo:facebook/react
About this issue
- Original URL
- State: open
- Created 2 years ago
- Reactions: 34
- Comments: 19
Also getting this with React Dev Tools + Storybook
Heve the same issue using
React Developer Tools
for Chrome inStorybook 7.0.7 for react-webpack5
Same issue
Saw this today:
Noticed my Chrome was out of date. After updating, no longer saw the error.
New version
Version 110.0.5481.100 (Official Build) (x86_64)
running MacOS 13.2 (22D49)