Skip to content

Conversation

hoxyq
Copy link
Contributor

@hoxyq hoxyq commented May 12, 2023

Summary

Initially reported in #26797. Was not able to reproduce the exact same problem, but found this case:

  1. Open corresponding codepen from the issue in debug mode
  2. Open components tab of the extension
  3. Refresh the page

Received multiple errors:

  • Warning in the Console tab: Invalid renderer id "2".
  • Error in the Components tab: Uncaught Error: Cannot add node "3" because a node with that id is already in the Store.

This problem has occurred after landing a fix in #26779. Looks like Chrome is keeping the injected scripts (the backend in this case) and we start backend twice.

@facebook-github-bot facebook-github-bot added CLA Signed React Core Team Opened by a member of the React Core Team labels May 12, 2023
@hoxyq hoxyq merged commit 67a05d0 into facebook:main May 12, 2023
@hoxyq hoxyq deleted the devtools/fix-duplicated-backend-activation branch May 12, 2023 13:59
hoxyq added a commit that referenced this pull request May 17, 2023
Closes #26787,
#26793

Includes these changes:
* fix[devtools]: fixed duplicated backend activation with multiple
renderers ([hoxyq](https://github.com/hoxyq) in
[#26807](#26807))
EdisonVan pushed a commit to EdisonVan/react that referenced this pull request Apr 15, 2024
…erers (facebook#26807)

## Summary
Initially reported in facebook#26797.
Was not able to reproduce the exact same problem, but found this case:

1. Open corresponding codepen from the issue in debug mode
2. Open components tab of the extension
3. Refresh the page

Received multiple errors:
- Warning in the Console tab: Invalid renderer id "2".
- Error in the Components tab: Uncaught Error: Cannot add node "3"
because a node with that id is already in the Store.

This problem has occurred after landing a fix in
facebook#26779. Looks like Chrome is
keeping the injected scripts (the backend in this case) and we start
backend twice.
EdisonVan pushed a commit to EdisonVan/react that referenced this pull request Apr 15, 2024
Closes facebook#26787,
facebook#26793

Includes these changes:
* fix[devtools]: fixed duplicated backend activation with multiple
renderers ([hoxyq](https://github.com/hoxyq) in
[facebook#26807](facebook#26807))
bigfootjon pushed a commit that referenced this pull request Apr 18, 2024
…erers (#26807)

## Summary
Initially reported in #26797.
Was not able to reproduce the exact same problem, but found this case:

1. Open corresponding codepen from the issue in debug mode
2. Open components tab of the extension
3. Refresh the page

Received multiple errors:
- Warning in the Console tab: Invalid renderer id "2".
- Error in the Components tab: Uncaught Error: Cannot add node "3"
because a node with that id is already in the Store.

This problem has occurred after landing a fix in
#26779. Looks like Chrome is
keeping the injected scripts (the backend in this case) and we start
backend twice.

DiffTrain build for commit 67a05d0.
Akshato07 pushed a commit to Akshato07/-Luffy that referenced this pull request Feb 20, 2025
Closes facebook/react#26787,
facebook/react#26793

Includes these changes:
* fix[devtools]: fixed duplicated backend activation with multiple
renderers ([hoxyq](https://github.com/hoxyq) in
[#26807](facebook/react#26807))

DiffTrain build for commit facebook/react@2468a87.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed React Core Team Opened by a member of the React Core Team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants