search

facebook / react

The library for web and native user interfaces.
https://react.dev
MIT License
229.08k stars 46.86k forks source link

[DevTools Bug]: shows "This page doesn't appear to be using React" for every react website on Firefox 115.0.2 #27158

Open anvesh-vanam opened 1 year ago

anvesh-vanam commented 1 year ago

Website or app

all of them and also localhost. https://react.dev/ for example

Repro steps

  1. open any website made with React
  2. Click on the extension icon

OS: Windows 10

Browser: Firefox 115.0.2 (64-bit)

DevTools: 4.27.8

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

github-actions[bot] commented 1 year ago

@anvesh-vanam: We're sorry you've seen this error. ❤️

Unfortunately the URL you provided ("localhost") is not publicly accessible. (This means that we will not be able to reproduce the problem you're reporting.)

Please help us by providing a link to a CodeSandbox (https://codesandbox.io/s/new), a repository on GitHub, or a minimal code example that reproduces the problem. (Screenshots or videos can also be helpful if they help provide context on how to repro the bug.)

Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve

Issues without repros are automatically closed but we will re-open if you update with repro info.

hoxyq commented 1 year ago

Hey @anvesh-vanam, thanks for opening this issue.

  1. Are you using device toolbar (ctrl + shift + m) with some selected device? This may change user agent and we currently aware of this problem.
  2. Has this problem occurred after upgrading Firefox? Does it work with previous versions?
anvesh-vanam commented 1 year ago

@hoxyq Hi.

  1. i sometimes do. but it happens regardless of whether im using it or not.
  2. i dont remember exactly but i think this has been happening for 2-3 weeks now, which seems to coincide closely with the 115.0.2 release date. i am on 115.0.3 facing the same issue
JesseKoldewijn commented 1 year ago

Hey @anvesh-vanam for me reinstalling the the extension when noticing this behavior did the join. Had the same issue on Chrome a couple of times.

anvesh-vanam commented 1 year ago

Hey @anvesh-vanam for me reinstalling the the extension when noticing this behavior did the join. Had the same issue on Chrome a couple of times.

tried it multiple times. unfortunately didnt work.

apicgg commented 1 year ago

@anvesh-vanam Try upgrading Firefox to v.116.0.1. Is this issue only occurring on windows?

JesseKoldewijn commented 1 year ago

Can confirm that the before mentioned issue doesn't occur on the latest firefox dev-ed on win11. Personally haven't experienced this issue on any browser in linux yet.

anvesh-vanam commented 1 year ago

@anvesh-vanam Try upgrading Firefox to v.116.0.1. Is this issue only occurring on windows?

i upgraded to 116.0.1. the issue is still there. yeah im only using windows 10

JesseKoldewijn commented 1 year ago

Shouldn't matter all that much. Could you try the firefox developer edition to see if that one does work?

anvesh-vanam commented 1 year ago

Shouldn't matter all that much. Could you try the firefox developer edition to see if that one does work?

yeah i just installed developer edition and its working fine on that one

apicgg commented 1 year ago

@anvesh-vanam I am not able to reproduce this issue in my windows machine. Good to hear that it's working with dev edition of Firefox.

JesseKoldewijn commented 1 year ago

Hey man, it seems to be a running issue that the dev tools sometimes break on older browser revisions. Experienced this with multiple releases over the past 2 years to be honest and either running dev/beta browsers or reinstalling the full browser itself usually does the job.

coderdix24 commented 1 year ago

having the same issue in mac the firefox developer edition 117.0b8 (64-bit)

I see the __REACT_DEVTOOLS_BREAK_ON_CONSOLE_ERRORS__ configuration in the DOM console, however running !!window.React in the console log comes back false.

And in the extension pin getting the error that this page isn't a react page.

henricook commented 8 months ago

Also having this problem on 118.0.2 - did you ever find a fix?

!!window.React is false for me also

JesseKoldewijn commented 8 months ago

Also having this problem on 118.0.2 - did you ever find a fix?

!!window.React is false for me also

Have you tried reinstalling the extension?

henricook commented 8 months ago

Have you tried reinstalling the extension?

Yes, no change.

Edit: it works on the react test site, just not on my local next.js app. Although the extension works fine in Chrome on my local next.js app. Could be a Vercel bug, maybe disregard me 😅

JesseKoldewijn commented 8 months ago

Have you tried reinstalling the extension?

Yes, no change.

Edit: it works on the react test site, just not on my local next.js app. Although the extension works fine in Chrome on my local next.js app. Could be a Vercel bug, maybe disregard me 😅

Maybe try again after a browser reinstall? From what I've personally noticed, either worked for me.