react-konva Error: Could not find ID for Fiber "App"

The error occurs opening react-konva examples: react_devtools_backend.js:5731 Uncaught Error: Could not find ID for Fiber "App" at getFiberIDThrows (react_devtools_backend.js:5731) at recordMount (react_devtools_backend.js:6361) at mountFiberRecursively (react_devtools_backend.js:6459) at mountFiberRecursively (react_devtools_backend.js:6507) at react_devtools_backend.js:6910 at Set.forEach (<anonymous>) at Object.flushInitialOperations (react_devtools_backend.js:6891) at react_devtools_backend.js:14252 at <anonymous>:201:34 at Array.map (<anonymous>) at Object.emit (<anonymous>:201:24) at attachRenderer (react_devtools_backend.js:14279) at react_devtools_backend.js:14291 at Map.forEach (<anonymous>) at initBackend (react_devtools_backend.js:14290) at setup (react_devtools_backend.js:10996) at welcome (react_devtools_backend.js:10942)

Env: Browser: Chrome 90.0.4430.212 OS: MacOS React Dev Tools: 4.13.4 (5/20/2021)

Examples:

'How to draw images on canvas with React?' https://ox106pyo65.csb.app/
'Drawing canvas shapes with React' https://w0oz80qqw8.csb.app/

May 22 '21 00:05 Throttle

Still reproducing by switching to standalone https://github.com/facebook/react/tree/master/packages/react-devtools

May 22 '21 00:05 Throttle

I'm getting the same thing in my own test app. Not sure what's causing it? Also when using react dev tools I can only see a 'StageWrap' component in the tree, but no other children of that (layers, groups, rect, etc.) is that the expected behavior?

May 25 '21 22:05 wilsmex

To me that looks like an issue with React Dev Tools. Probably it doesn't like custom renderers (such as react-konva). I am not sure what we can do from react-konva side.

Personally I am not interested much in finding the solution, because I am not using React Dev Tools and I just ignore the message.

But any help is very welcome. Probably we should ask in React Dev Tools repo.

May 25 '21 23:05 lavrton

I'm sure some change to DevTools caused this problem. Until a few days ago, I did not have this error. And I haven't updated any dependencies in the meantime.