React: Bug: Chrome DevTools failed to load SourceMap after upgrade to Chrome 86.0.4240.111

Created on 24 Oct 2020  路  1Comment  路  Source: facebook/react

React DevTools version: 4.9.0-75726fadfd

Steps To Reproduce

  1. Install React DevTools into Chrome 86
  2. Observe Chrome errors loading source maps for React DevTools.

Link to code example:

None

The current behavior

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

The expected behavior

Show no errors.

Workaround

  • Disable JavaScript source maps in Chrome DevTools (Open Chrome DevTools, click three dots menu in upper right corner, find Settings under More Tools. Uncheck "Enable JavaScript source maps".)

Workarounds that don't work:

  • Remove all .map files in ~/.config/google-chrome/Default/Extensions/fmkadmapgofadopljbjfkapdkoienihi/4.9.0_0/build/.
  • Remove all .map files from ~/.config/google-chrome/Default/Extensions/fmkadmapgofadopljbjfkapdkoienihi/4.9.0_0/
  • Edit each .js file in ~/.config/google-chrome/Default/Extensions/fmkadmapgofadopljbjfkapdkoienihi/4.9.0_0/build/ to remove the line with //# sourceMappingURL=. This changes the hash of each file and Chrome will refuse to load the extension.

Other Notes

  • OS: Manjaro Linux
Developer Tools Duplicate Unconfirmed Bug

Most helpful comment

I'm sorry you experienced this bug! 馃檱

Looks like this problem was already reported though (#20075) so I'm going to mark this issue as a duplicate and close it. That issue has already been fixed and the fix will be released shortly.

>All comments

I'm sorry you experienced this bug! 馃檱

Looks like this problem was already reported though (#20075) so I'm going to mark this issue as a duplicate and close it. That issue has already been fixed and the fix will be released shortly.

Was this page helpful?
0 / 5 - 0 ratings