Error: "Cannot add node "1" because a node with that id is already in the Store."

[dharapx]

Which website or app were you using when the bug happened?

Please provide a link to the URL of the website (if it is public), a CodeSandbox (https://codesandbox.io/s/new) example that reproduces the bug, or a project on GitHub that we can checkout and run locally.

What were you doing on the website or app when the bug happened?

If possible, please describe how to reproduce this bug on the website or app mentioned above:

Generated information

DevTools version: 4.13.1-93782cfed2

Call stack:
(none)

Component stack:
(none)

GitHub URL search query:
https://api.github.com/search/issues?q=Cannot%20add%20node%20%20because%20a%20node%20with%20that%20id%20is%20already%20in%20the%20Store.%20in%3Atitle%20is%3Aissue%20is%3Aopen%20is%3Apublic%20label%3A%22Component%3A%20Developer%20Tools%22%20repo%3Afacebook%2Freact

[bvaughn]

@dharapx Sorry you hit this problem

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

Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a repository on GitHub, or provide 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

[ZackeryBayle]

Project: https://github.com/ZackeryBayle/TrollyReactJS
Back end: https://github.com/ZackeryBayle/TrollyCRM

While working on the project doing some code splitting.

Update existing issue: Error: "Cannot add node "1" because a node with that id is already in the Store." Uncaught Error: Cannot add node "1" because a node with that id is already in the Store.
I am pretty new so please forgive the crazy mess you are about to witness.

[bvaughn]

Hey @ZackeryBayle! This is a great help.

While working on the project doing some code splitting.

Can you elaborate a little more on what I'd need to do to reproduce the error myself beyond running these two projects locally?

[ZackeryBayle]

@bvaughn - I was working on just rendering some props on the home screen after splitting my form code into its own component.
On render throws error
Page still renders

I hope that helps, let me know if there is anything else I can provide.

[ZackeryBayle]

I have simply removed everything from the rendering page (home.js) and the error still happens. The only thing being rendered is my navBar and footer. Nothing has changed on these components for weeks. I haven't done any updates to dependence.

[bvaughn]

Oh that's excellent. Can you push a branch and point me at it so I can check it out and repro?

I got stuck having to install mongodb this morning to run the backend and then I had meetings.

[ZackeryBayle]

Here is the new branch https://github.com/ZackeryBayle/TrollyReactJS/tree/staging-issues

[bvaughn]

Thanks!

[bvaughn]

@ZackeryBayle So you just load the page and see the error?

I can't repro that. (Now that Mongo is installed.)

Do you have any component filters or anything on in your devtools by chance? Would I need any dummy data in my mongodb to repro this maybe?

[ZackeryBayle]

correct Just loading the page produces that error. Nothing about the mongo should any effect on this atm because all the components have been removed from the pages/home.js

I don't know what a component filter is sorry I'm really new at this. This is actually my capstone project for bootcamp.

[bvaughn]

Ah ok that's interesting. I wonder why I'm not able to reproduce the bug using the same branch/app.

Any chance you'd be up for a quick Zoom call tomorrow to look at it together? No problem if you're not, but if you are– shoot me an email (brian.david.vaughn at gmail) or a DM on twitter (@ brian_d_vaughn)