No tab in Chrome 42 about react-devtools

[zpao]

Can you specify the React version you're testing with? For example, when I view the React website with Chrome 41, I can use the devtools. That's React v0.12.2.

It looks like most of the Chrome 40 reviews are before the latest update to devtools.

[sscotth]

I tend to do my dev work in Canary and maybe I had a pending update yesterday...

Using React Developer Tools 0.13.0 on OSX Yosemite 10.10.2.

Browsing to the react site works for me on Chrome Version 41.0.2272.64 beta (64-bit) but does not work on Version 42.0.2309.2 canary (64-bit).

[ngyikp]

DevTools on Chrome 42+ is currently bugged and only one extension panel can be loaded, try disabling any other extension that hooks into DevTools (e.g. EditThisCookie/SnappySnippet/HTTPS Everywhere)

https://code.google.com/p/chromium/issues/detail?id=460065

[ngyikp]

This seems to be fixed as of 42.0.2311.22 dev-m, so this issue should be resolved/closed.

[subblue]

The React devTools tab is also empty with Chrome 43.0.2327.5 dev

[Swaagie]

Could it be that no tab is showing if the page is simply loaded from file? No tab visible for both canary and 41.0.2272.118, but both versions do show the tab for the react website.

[nozpheratu]

I'm also experiencing the issue with the React tab not showing up when the page is loaded from the local file system. Using Chrome v43.0.2357.81 on Ubuntu. I see the tab when visiting an external page using React, however.

Edit:
Nevermind, needed to enable the Allow access to file URLs option in the settings.

[sophiebits]

Yes, I believe the extension does not work on file:// URLs due to a Chrome security restriction.

[nozpheratu]

@spicyj It worked for me by enabling the local file URLs setting.

[sophiebits]

Good point.

[jesstelford]

I was having this problem also, and no amount of reinstallation got it working. BUT! I managed to fix it by following these steps (I'm not sure which part fixed it though):

• Disable ALL extensions
• Load React app / note "React" tab missing from DevTools
• Re-enable React extension
• Note "React" tab still missing
• Allow React in Incognito mode
• Open new Incognito window
• Note "React" tab now shows
• Open new regular window
• Note "React" tab now shows
• Disallow React in Incognito mode
• Re-enable all the other extensions
• Note "React" tab still shows

The version of chrome is worked in: 45.0.2452.0 canary (64-bit)

[jaredly]

Has anyone had this issue with the new beta version. It's a complete rewrite, so my assumption is that this bug will have gone away...

[loganfuller]

Can confirm I'm still having this issue with the latest v0.14 in Chrome 44.0.2403.157 (64-bit) on OSX 10.11 Beta.

[sophiebits]

@loganfuller Can you link to a site where you see this problem?

[FutureKode]

Hi, with react dev tools v0.14, the tab does not show. If I click "Allow access to file url's" then chrome says "This extension may have been corrupted." so I click repair but still have same issues.

[hilkeheremans]

I did not have this issue in the beta version, but since the final release I am regularly getting the "This extension has been corrupted" message.

Only uninstalling, closing Chrome, reopening and reinstalling seems to resolve this until it, frustratingly, happens again. It occurs intermittently and does not seem to be related to any specific events.

Can't provide you with an example site since, unfortunately, confidential. Let me know if I can do anything else to help you track this down.

[loganfuller]

@spicyj turns out the problem was that my React app is being designed as a 3rd party embed and runs in an iframe. I used the code below as a fix and it works great now. Thanks for the awesome tools!

if (window.parent !== window) {
    window.__REACT_DEVTOOLS_GLOBAL_HOOK__ = window.parent.__REACT_DEVTOOLS_GLOBAL_HOOK__;
}