[DevTools Bug] Cannot remove node "XX" because no matching node was found in the Store.

[baptistemanson]

Website or app

https://ideaflow.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 [DevTools Bug]: React Devtools on Firefox initially shows an empty (blank) component tree #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

[dotjson01]

it doesn't look like this issue has enough info for one of us to reproduce it though. This means that it's going to be very hard for us to fix.
Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve

[inoyakaigor]

Got the same issue. Nothing to add except basic information about my app:
React@17.0.2
react-router@5.2.0
mobx@6.6.2
antd@4.23.1
typescript@4.8.3
App builded with webpack through ts-loader (means there is no Babel)

[Moskowitza]

This issue has arisen in our app only recently.
"react": "16.5.0"
"redux": "4.0.0"
"redux-persist": "5.10.0"
"webpack": "4.12.0",

[christina-kirk]

I don't know about anyone else but I'm noticing this issue is happening roughly the same time as an auto update of the react-native-debugger package.

The react-native-debugger client was prompting an upgrade that I kept ignoring but after running brew info react-native-debugger I can see the package is subscribed to auto-updates and the version was automatically bumped to v0.13.0

I'm also not seeing any way to deprecate the debugger client to an older version, so I also can't actually test the version theory.

[interhub]

I noticed that the problem occurs - when I'm looking for components nested in the ReactNativeSvg tree

[johnson-jesse]

Saw this today:

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)

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)

[christina-kirk]

Updating chrome resolved this for me also.

[TomasHubelbauer]

Still happens for me in up to date Firefox Version 110.0 (64-bit). Repeatable 100 % of the time. Do not have a minimal repro, just adding data points about liveness and frequency of the issue.

[UrUrZa]

Heve the same issue using React Developer Tools for Chrome in Storybook 7.0.7 for react-webpack5

[pankajsoni91]

I am also facing the same issue. The browser update resolved it once. But it is coming again and again.

[francisashley]

Also getting this with React Dev Tools + Storybook

[SwapnilSoni1999]

Also getting this with React Dev Tools + Storybook

Same issue