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.

Sign up for GitHub

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

Jump to bottom

[DevTools Bug]: Error: Could not find ID for Fiber "..." #23049

Closed
d-pollard opened this issue Dec 30, 2021 · 2 comments
Closed

[DevTools Bug]: Error: Could not find ID for Fiber "..." #23049

d-pollard opened this issue Dec 30, 2021 · 2 comments
Labels
Component: Developer Tools Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug Type: Bug

Comments

@d-pollard
Copy link

Website or app

https://github.com/d-pollard/react-konva-devtools-issue

Repro steps

  1. Install repo
  2. run repo
  3. visit /playground in your browser of choice.
  4. Navigate to the dev tools, and you should see the error

How often does this bug happen?

Every time

DevTools package (automated)

No response

DevTools version (automated)

No response

Error message (automated)

No response

Error call stack (automated)

No response

Error component stack (automated)

No response

GitHub query string (automated)

No response
@d-pollard d-pollard added Component: Developer Tools Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug Type: Bug labels Dec 30, 2021
@d-pollard d-pollard mentioned this issue Dec 30, 2021
Closed
@d-pollard d-pollard changed the title [DevTools Bug]: Error: Could not find ID for Fiber "" [DevTools Bug]: Error: Could not find ID for Fiber "..." Dec 30, 2021
@d-pollard d-pollard mentioned this issue Dec 30, 2021
Closed
@bvaughn
Copy link
Contributor

bvaughn commented Jan 20, 2022 •
edited
Loading

Possibly fixed by #23156.

Released on Jan 24 as version 4.23.0:
https://github.com/facebook/react/blob/main/packages/react-devtools/CHANGELOG.md#4230-january-24-2022

Give it a couple of days to propagate to all of the browsers. (Chrome usually takes the longest.)

@bvaughn
Copy link
Contributor

bvaughn commented Jan 21, 2022

Going to roll this into #22970 since they're both the same error and that one has more context. Will follow up there.

@bvaughn bvaughn closed this as completed Jan 21, 2022
@bvaughn bvaughn mentioned this issue Jan 21, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Component: Developer Tools Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug Type: Bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bvaughn @d-pollard