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

[AsheshL]

Website or app

Website

Repro steps

Not sure

How often does this bug happen?

Often

DevTools package (automated)

react-devtools-extensions

DevTools version (automated)

4.13.2-e468072e17

Error message (automated)

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

Error call stack (automated)

No response

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

[bvaughn]

Hi!

I'm sorry you ran into this problem.

Unfortunately, it doesn't look like this issue has enough info for one of us to reproduce it though.

Please help us by providing a link to a CodeSandbox (https://codesandbox.io/s/new), a repository on GitHub, or a minimal code example that reproduces the problem. (Screenshots or videos can also be helpful if they help provide context on how to repro the bug.)

Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve

We may close issues that have no repro.

[devxalted]

I've had this same issue, it happens when the DOM removes previously rendered components that are conditionally rendered using ternary operators and Context API state.

It's not bothersome enough for me to include all the code etc, but it does make it a littler harder to debug since I have to use console.log instead of viewing the current state of a component.

[bvaughn]

@AsheshL Without a repro, there's nothing I can do with this issue.

Here's an updated build of DevTools though that might fix the problem you're seeing, if you'd like to test it out:
ReactDevTools.zip

You can follow these steps to install it:
https://user-images.githubusercontent.com/29597/118749019-b6cda600-b82a-11eb-9449-ef56f41eced5.mp4

[JoelBrenstrum]

@bvaughn That unpacked extension worked for me! Thanks

[bvaughn]

Thanks!

I'm going to go ahead and close this since we still don't have any repro info. Hopefully the updated extension fixes the problem, but if not- we can re-open the issue later.