[DevTools Bug]: React devtools stuck at Loading React Element Tree, troubleshooting instructions are Chrome-specific #26911
Comments
ialexryan
added
Component: Developer Tools
Status: Unconfirmed
|
Hey @ialexryan, thanks for reporting this. Can you please check if there are any errors in the extension's console when you are trying to use it? In Firefox, this can be done via debugging add-ons: Then click 'Inspect' for DevTools extension and you should be able to check the console. |
|
I'm having the same issue. This is what comes up in the console: |
|
I actually hit this for the first time in a while just now. The error in the console was |
|
Same issue but nothing in the console. |
|
Also same problem. Nothing in console. |
|
Hey, I've opened a PR with changes that should fix it - #27179. Looks like extension doesn't work when mobile dev mode is enabled in Firefox. Can anyone try downloading and installing a custom build from here to check if it fixes the problem for you?
|
|
@hoxyq That fixed it for me! Thanks! |
…n user agent (#27179) Fixes #26911, #26860. Currently, we are parsing user agent string to determine which browser is running the extension. This doesn't work well with custom user agents, and sometimes when user turns on mobile dev mode in Firefox, we stop resolving that this is a Firefox browser, extension starts to use Chrome API's and fails to inject. Changes: Since we are building different extensions for all supported browsers (Chrome, Firefox, Edge), we predefine env variables for browser resolution, which are populated in a build step.
…n user agent (facebook#27179) Fixes facebook#26911, facebook#26860. Currently, we are parsing user agent string to determine which browser is running the extension. This doesn't work well with custom user agents, and sometimes when user turns on mobile dev mode in Firefox, we stop resolving that this is a Firefox browser, extension starts to use Chrome API's and fails to inject. Changes: Since we are building different extensions for all supported browsers (Chrome, Firefox, Edge), we predefine env variables for browser resolution, which are populated in a build step.
Website or app
corporate project (private)
Repro steps
Load page, then open React DevTools. Reloading or closing and reopening the tab does not fix the problem. Quitting and reopening Firefox sometimes fixes the problem.
The linked troubleshooting instructions provide no guidance for users of browsers other than Chrome; I am running Firefox v114 (on macOS 13.2.1).
How often does this bug happen?
Often
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
The text was updated successfully, but these errors were encountered: