Fails to load in Chrome 35, "Cannot read property 'injectedScript' of undefined" about react-devtools

[coolzilj]

Same problem.
Chrome 35.0.1916.153

[zpao]

I just tested with a new users and the same version but didn't have that issue. Perhaps OS related?

[atombender]

OS X here.

[tsimons]

Same issue for me. I just reinstalled the extension and the same problem occurs.

OSX Mavericks
Chrome Version 35.0.1916.153

[palcu]

👍 same problem same versions as @tsimons

[haohcraft]

same problem same version as up

[yofine]

same problem same version as up

[jcurtis]

Same issue on Chrome Version 36.0.1985.125 on OS X 10.9.4

[enricribas]

Same here. Any news guys? Comments say to expose React as global but that doesn't help.

[zpao]

@enricribas your problem sounds different than this issue, which is that the extension doesn't load at all.

[zpao]

I have what might be a fix. I can't reproduce though so I have no idea what this will or will not fix. The diff is in #43. I packed the extension and have a crx file if anybody is willing to give it a try: http://cl.ly/WqYL

@enricribas, I may have jumped to conclusions about your case. Sorry!

[tsimons]

@zpao I just loaded that extension. The error goes away, but the tools don't load. I get the:

Download the React DevTools for a better development experience: http://fb.me/react-devtools

message in my console from React, and the background page of the extension has no errors.

[hawkrives]

(chrome v. 36.0.1985.125, OS X 10.9.4)

@zpao: I've got the same result as @tsimons. The error goes away, the React devtools don't load, and the DEVTOOLS_INJECTED_SCRIPT key in localStorage is set to function(){console.error("undefined")}.

Edit: But it might just be my app; the test page loads the React tools perfectly.

[zpao]

If the test page and the React website work, then I'm going to blame your app. Make sure you export React to the window, as mentioned in the readme. If you can inspect anything, I think this fix is fine. Let me know!

[tsimons]

Exposing react to window worked for me. Thanks for pointing that out.

Would it be possible to modify the script that logs the "download devtools" message to also check for window.React?

[hawkrives]

Yeah, it now works for me, too.

The only thing is, I was already explicitly exposing window.React, but I'll just chalk it up to one of those oddities in computers.

Thanks, guys.

[atombender]

Works for me, too, even without the fix from @zpao.

[zpao]

Thanks for testing! I'll get the fix merged in and make sure we push out an update.

Would it be possible to modify the script that logs the "download devtools" message to also check for window.React?

We're (slowly) working on better solution there. Simply checking for window.React isn't enough and actually wouldn't work at the point we log that message.

[tsimons]

Yeah I realized that after I had submit... haha.

I also noticed one thing that related to some confusion here, and this is probably due to my lack of chrome extension knowledge. The script that loads the extension in the chrome inspector panel only runs when you first visit a site. For instance, I added window.React = React to my app, then refreshed my currently open page and nothing happened. When I opened a new tab and visited my app again, the react tab appeared. Hopefully this clears up some confusion for someone else!