react: [DevTools Bug] Cannot remove node "612" because no matching node was found in the Store.
Website or app
proprietary
Repro steps
Overall, testing and refactoring of a component containing a formik wrapped form which includes a fieldarray with yup schema. Using VS Code to serve the React js application.
Unable to share the repo / website as it is proprietary.
Task: Logged in to the app to see the form as the specific user role required to see the component, testing yup schema on formik elements touched property to do some custom error connections in the containing component with React Developer Tools open to the Components view with the console also open.
I was verifying the elements described in the schema file were getting ‘touched’ and was refining a select in yup schema js file.
Switched one element’s schema property from yup.object() to yup.int() triggers the error. This is a syntax error. Should be yup.number(). But switching the two causes it all to crash.
“formik”: “^2.2.6”, “prop-types”: “^15.7.2”, “react”: “^17.0.2”, “react-router-dom”: “4.3.1”, “react-select”: “^4.3.0”, “yup”: “^0.26.10” “yarn”: “^1.13.0”,
“babel-eslint”: “^10.1.0”,
How often does this bug happen?
Every time
DevTools package (automated)
react-devtools-extensions
DevTools version (automated)
4.23.0-e28a0db22
Error message (automated)
Cannot remove node “612” because no matching node was found in the Store.
Error call stack (automated)
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:26349:43
at bridge_Bridge.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:24415:22)
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:24581:14
at listener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:54033: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: 1
- Comments: 26 (11 by maintainers)
Ah sorry @lunaruan but Shipt is closed source. I wonder, did you test on the react native version that was experiencing this problem? We’re on 0.65.x. I assume this isn’t worth hotfixing, you can probably just have this ticket serve as the solution for people still on older versions.
You’re right @bvaughn it was just swallowing the error and neither the profiler tab nor the component tab were working. I’ve now isolated to no errors whatsoever. I did it by locking react native’s transitive
react-devtools-coreto4.7.0(rather than ^4.6.0) and installed global devtools withyarn global add react-devtools@4.7.0.The break happens betweenreact-devtools4.7.0…4.8.0. I suspect React Native has not locked to the correct transitive version, which is why you guys can’t reproduce this. They just need to remove the^from their transitive dependency on react-devtools-core in package.json. For backwards compat the fix is probably between those two versions. I’ll update my previous comment to point here.4.7.0 success, both components and profiler working:
I am having the same issue when trying to switch the component rendered inside a Suspense.
react-devtools version: 4.24.3-46a98cff2
Demo: https://codesandbox.io/s/amazing-blackburn-k2iql8?file=/src/App.js
I got this error using react-devtools 4.24.1.
Reinstalling npm install react-devtools@4.2 solved my issue. (Also possible a fresh install helped.)
Also FWIW with 4.24.1, I had an issue where react-devtools loaded and seemed to connect but no components displayed (filters were removed).
@mrkev Why are you using a year old version of DevTools? 😃
@RobIsHere Thanks for commenting! Unfortunately, without a reproducible repro on our side, we’re unable to debug this issue. Could you create a repro of this on Code Sandbox? Thanks!