DevTools icon indicating copy to clipboard operation
DevTools copied to clipboard

Edge 142 breaks React DevTools

Open AzureZeng opened this issue 1 month ago • 10 comments

After updating to v142.0.3595.53, React DevTools is broken, saying "Looks like this page doesn't have React, or it hasn't been loaded yet."

Tested on Chrome 142 and Edge 141, and there are no such bug.

Image

AzureZeng avatar Nov 02 '25 13:11 AzureZeng

Same issue.

Test with React DevTools 7.0.1 and 6.1.5. Both can't run on Edge 142.

(React DevTools 7.0.1 + Chrome 142 is ok.)

Looks like this page doesn't have React, or it hasn't been loaded yet.

Use Ctrl+Shift+I open DevTools for DevTools.

console log

Extension server error: Operation failed: Permission denied
e @ extensions.js:5
onmessage @ extensions.js:5

exception

Session is unregistering, can't dispatch pending call to Runtime.evaluate"

ganlvtech avatar Nov 03 '25 09:11 ganlvtech

Same issue on macOS arm64 Edge 142.0.3595.53. Also, once you activate React DevTools Components or Profiler tabs, the DevTools panel cannot be closed.

  • switch to old DevTools not work
  • enable allow access to file urls not work
  • reinstall React DevTools/Edge not work

wxupjack avatar Nov 03 '25 10:11 wxupjack

This seems to be a general issue with the DevTools, since ArcToolkit is also not working anymore.

ARC Toolkit Extension in DevTools

Also when switching the position of the DevTools, while being on a "broken" extension (eg.: from bottom to right or vice versa) the layout gets messed up. In that case, the close-icon of the DevTools is no longer working. They can only be closed through a key-combo in that case (CMD + ALT + I).

Broken DevTools Layout after switching position

saschadiercks avatar Nov 04 '25 06:11 saschadiercks

Using React DevTools also breaks all the built-in tools: Elements, Console, Sources - nothing works until you reopen the DevTools window. Edge QA is a joke (not a funny one)

SunsetTechuila avatar Nov 04 '25 17:11 SunsetTechuila

Thank you all for sharing details on this issue. The engineering team is currently looking into this.

leahmsft avatar Nov 04 '25 21:11 leahmsft

Also, the Vue.js devtools https://chromewebstore.google.com/detail/vuejs-devtools/iaajmlceplecbljialhhkmedjlpdblhp?pli=1

dews avatar Nov 05 '25 11:11 dews

Same issue on macOS arm64 Edge 142.0.3595.53. Also, once you activate React DevTools Components or Profiler tabs, the DevTools panel cannot be closed.

  • switch to old DevTools not work
  • enable allow access to file urls not work
  • reinstall React DevTools/Edge not work

Not just that, you also cannot refresh the page at all either, you have to close the tab and open a new tab. So, it pretty much breaks the entire tab.

jonathan-x01 avatar Nov 05 '25 20:11 jonathan-x01

This is very annoying, it is not working for my next.js projects too I had to move to npx react-devtools for now

omarqra avatar Nov 06 '25 08:11 omarqra

Same goes for GraphQL Network Inspector https://chromewebstore.google.com/detail/graphql-network-inspector/ndlbedplllcgconngcnfmkadhokfaaln

seanputera avatar Nov 06 '25 22:11 seanputera

I updated to Version 142.0.3595.65 (Official build) (64-bit) this morning and it has not fixed the issue. Vue.js dev tools extension will still cause Edge dev tools to lock up the whole tab until it is closed and reopened - making Vue development in Edge extremely difficult.

Vue.js dev tools extension continues to work as expected in Chrome Version 142.0.7444.135 (Official Build) (64-bit)

tsulli avatar Nov 07 '25 13:11 tsulli

I upgraded to version 142.0.3595.69 and the issue is resolved.

HadarZ avatar Nov 09 '25 08:11 HadarZ

Image

Confirmed that this issue is solved by updating Microsoft Edge.

AzureZeng avatar Nov 10 '25 04:11 AzureZeng

Confirmed that this issue is solved by updating Microsoft Edge.

What your current Edge version? Mine is 142.0.3595.65. It works at the first time, but still crashes after several attempts.

wxupjack avatar Nov 10 '25 04:11 wxupjack

Confirmed that this issue is solved by updating Microsoft Edge.

What your current Edge version? Mine is 142.0.3595.65. It works at the first time, but still crashes after several attempts.

I found this, so I reopend this issue.

AzureZeng avatar Nov 10 '25 04:11 AzureZeng

Confirmed that this issue is solved by updating Microsoft Edge.

What your current Edge version? Mine is 142.0.3595.65. It works at the first time, but still crashes after several attempts.

Seems 142.0.3595.69 is ONLY available in Windows platform so Mac/Linux user still need to wait for the 142.0.3595.69 patch.

AzureZeng avatar Nov 10 '25 13:11 AzureZeng

Can confirm that 142.0.3595.69 fixes the issue.

bobvandevijver avatar Nov 10 '25 13:11 bobvandevijver

Thank you all for your patience. The fix is in v142.0.3595.69 which was only released to Windows, and it will be available for Mac/Linux in the release this Thursday (11/13).

Thank you again for reporting these issues and helping us improve the product. The engineering team is committed to enhancing testing to prevent this issue in the future.

leahmsft avatar Nov 11 '25 00:11 leahmsft

Thank you again for reporting these issues and helping us improve the product.

It's a disgrace that your team didn't catch such an obvious and serious issue. You should be sorry, not thankful

SunsetTechuila avatar Nov 11 '25 06:11 SunsetTechuila