Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DevTools Error] Cannot remove node "145" because no matching node was found in the Store. #21529

Closed
youssouf-marzouk opened this issue May 19, 2021 · 4 comments
Labels
Component: Developer Tools Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug Type: Bug

Comments

@youssouf-marzouk
Copy link

Website or app

https://github.com/marzouk2002/GetItDone/blob/master/client/src/components/Login.js

Repro steps

After login with email and password, and the validation from the server. This happen when I tried to redirect to the home page

How often does this bug happen?

Every time

DevTools package (automated)

react-devtools-extensions

DevTools version (automated)

4.13.2-e468072e17

Error message (automated)

Cannot remove node "145" because no matching node was found in the Store.

Error call stack (automated)

at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:21477:43
    at bridge_Bridge.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:19585:22)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:19745:12
    at listener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:37733: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
@youssouf-marzouk youssouf-marzouk added Component: Developer Tools Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug Type: Bug labels May 19, 2021
@bvaughn
Copy link
Contributor

bvaughn commented May 19, 2021

This issue has been fixed in version 4.13.3 which is currently in-review in Chrome, Firefox, and Edge stores :)

Sorry for the trouble! Give it a few for the update to roll out, then this should be fixed.

@bvaughn bvaughn closed this as completed May 19, 2021
@youssouf-marzouk
Copy link
Author

Ohh I see, thanks.

@ewotring
Copy link

This appears to be persisting. I'm up to version 4.13.4.

@bvaughn
Copy link
Contributor

bvaughn commented May 25, 2021

@ewotring Comments on closed issues are generally ignored. If you're seeing this bug on 4.13.4, please open an issue that includes source code and steps for how to trigger the bug and I'll be happy to look 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Developer Tools Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug Type: Bug
Projects
None yet
Development

No branches or pull requests

3 participants