[DevTools Bug]: components tree not loaded in Microsoft Edge

[HadarZ]

Website or app

https://react.dev/

Repro steps

1. Load react app in Microsoft Edge
2. Open dev tools and go to components tree
3. The tree is not loaded:
4. This is the message I get: Loading React Element Tree... If this seems stuck, please follow the troubleshooting instructions.

Edge version - latest: Microsoft Edge
Version 112.0.1722.58 (Official build) (64-bit)

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

[krotovic]

I also stumbled upon this issue and it's really bad for me as I work as React developer and need this extension daily.

This is what I found in the console of the extension; hope it helps.

Also I use the latest version from Chrome extension store.

[hoxyq]

Hey @HadarZ,

Thanks for reporting this. We have recently published version 4.27.6 for Edge browser with a possible fix for this issue. Could you please try it out?

[HadarZ]

@hoxyq Thank you so much! I removed the extension and installed the new version, it's working now.

[hoxyq]

I also stumbled upon this issue and it's really bad for me as I work as React developer and need this extension daily.

This is what I found in the console of the extension; hope it helps.

Also I use the latest version from Chrome extension store.

Hey @krotovic, since your problem is not related to Edge, could you please open a separate issue for it? Please also provide more details on how to reproduce this.

You might also wait a bit for version 4.27.6 to be available for Chrome and then report if you still facing this problem.

Closing this issue.

[krotovic]

@hoxyq Since I posted here the comment I tried to investigate a little further and found that the console error is probably not related to the issue as the comment in the related code says here.

Also after I updated the extension everything works and no error in the console as well.