React version: 16.x.x
Looks to be related to https://github.com/facebook/react/pull/19773
Link to code example:
Console logs about failure to load source maps
No console logs because of the extension
I have the same warning, and my componet is always loading.
but it works on 4.8.2
I have the same warning in React^17.0.0 too
Sorry about the hassle here. I'm not sure why Chrome is showing this warning, as the source map URLs are correct. If anyone would like to dig into this, I'd welcome the help.
@hqwuzhaoyi Your comment does not seem related to this thread. If you're seeing a problem with a component's props loading, please file a separate issue with repro instructions.
Looks like a potentially related CR bug from back in February: https://bugs.chromium.org/p/chromium/issues/detail?id=1052872
A simple fix for this might be to revert the changes from #19773 to files within packages/react-devtools-extensions
(but leave the other packages with source maps enabled).
@bvaughn I tried reverting the changes in packages/react-devtools-extensions
and it fixed. Please help to review the PR #20079. Thanks.
Thanks for the quick work @bvaughn @sytranvn
We've run into similar issues with our own chrome extension so no big deal :D
Still having this issue. It looks like my React DevTools extension is still on version 4.9.0.
How do I get the version with the fix that was merged above? Removing and re-adding the extension didn't work. Sorry for the rookie question, but I'm sure others will be landing here with the same question.
The fix has not been released. You're running the latest DevTools. Once this fix gets releasd, Chrome will update you.
Oh, I see. Thank you!
I don't know if is of any help for fixing the bug, but anyhow sharing my experience, some of the messages did not appear anymore in Chrome after I right-clicked the React Dev Tool extension icon in the toolbar, clicked "manage extension" (I'm freely translating menu text here since my browser language is in Brazilian Portuguese), and then enabled "Allow access to files URLs."
I don't know if is of any help for fixing the bug, but anyhow sharing my experience, some of the messages did not appear anymore in Chrome after I right-clicked the React Dev Tool extension icon in the toolbar, clicked "manage extension" (I'm freely translating menu text here since my browser language is in Brazilian Portuguese), and then enabled "Allow access to files URLs."
This unfortunately doesn't work for me.
Console still polluted by:
DevTools failed to load SourceMap: Could not load content for chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/injectGlobalHook.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME
DevTools failed to load SourceMap: Could not load content for chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/react_devtools_backend.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME
DevTools failed to load SourceMap: Could not load content for chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/contentScript.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME
As I said above, the fix for this has not been released yet. Releasing DevTools takes a decent amount of time and I haven't had the time to publish an update yet.
be patient guys
Version 4.10 has been published to NPM and posted to Chrome/Firefox/Edge stores. Chrome usually takes a while to approve (hours, sometimes days).
Most helpful comment
I don't know if is of any help for fixing the bug, but anyhow sharing my experience, some of the messages did not appear anymore in Chrome after I right-clicked the React Dev Tool extension icon in the toolbar, clicked "manage extension" (I'm freely translating menu text here since my browser language is in Brazilian Portuguese), and then enabled "Allow access to files URLs."