1passwordX sourcemap issue adding warning to Chrome Console

as42

I'm a web dev and use the chrome developer console on a daily basis.

I see a warning message almost each time

DevTools failed to parse SourceMap: /Google/Chrome/Default/Extensions/aeblfdkhhhdcdjpifhhbdiojplfjncoa/1.18.0_0/inline/injected.js.map

I looked it up, and it seems to be coming in from 1passwordX. I can confirm that disabling the extension removes the message. This isn't a big issue, but is a minor inconvenience. I don't see any such warning from any other extension I have installed.

---

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided

ag_ana

Hi @as42! Welcome to the forum!

Can you please let us know what version of 1Password X this is happening with, and on what version of Chrome?

as42

Hello,

Chrome version 80.0.3987.106
1passwordX version 1.18.0

I can verify that this doesn't happen on Windows, only macOS

kaitlyn

Thanks for the additional info, @as42. I'm wondering what you're doing when you see that error. I haven't been able to get it to show up in the console myself (on macOS). Let me know!

as42

@kaitlyn yeah, it's rather strange, but it appears to be an issue on Chrome's end. Here's a screenshot of it happening:

However, one thing to note is turning on "Selected context only" hides the warning. Upon further investigation there's an open issue in Chrome about this warning affecting other extensions - https://bugs.chromium.org/p/chromium/issues/detail?id=1052872

kaitlyn

@as42 – Super interesting! Thanks for finding the open Chromium issue. That sounds like what you're experiencing. I'm not sure there's anything I'd be able to do on my end, though.

as42

Absolutely, you can mark this "closed" for now :)

Thank you for your time.

tychotithonus

Also happening on Linux(es).

ag_ana

@as42:

Thank you for the updates on this :) If you have any other questions, please feel free to reach out anytime.

Have a wonderful day :)

ag_ana

@tychotithonus:

Since this is a Chrome issue, it makes sense that it is happening even on Linux. You can find all updates on the issue in the link posted above by as42.

palpie

Also happens in Windows 10. At least for 1Password X 1.18.0 in Chrome 80.0.3987.149 and 1Password X 1.18.1 in Edge 80.0.361.109.

ag_ana

@palpie:

Thank you for the confirmation :+1: Because this seems to be a Chrome issue, I am not surprised if this is also happening with Edge on Windows 10, since it's based on Chrome.

fiokins

Also happening on Firefox 74.0 on Fedora Linux.

Source map error: Error: NetworkError when attempting to fetch resource.
Resource URL: moz-extension://2940e614-cb73-48f4-9acc-18b2b7c3fb33/inline/injected.js
Source Map URL: injected.js.map

The buildinfo reports the following:

moz-extension://2940e614-cb73-48f4-9acc-18b2b7c3fb33/build.info
{"buildnum":"20102","builddate":"2020-03-12 16:42:33","buildchannel":"stable","artists":["Dave Teare","Dan Peterson","Mitch Cohen","Andrew Beyer","Jasper Patterson","Jamie Phelps","Dan Kyung","Dalton Downing"]}

And the error makes sense, there is no sourcemap for the injected JS file present:

moz-extension://2940e614-cb73-48f4-9acc-18b2b7c3fb33/inline/
300: jar:file:///home/leehambley/.mozilla/firefox/rawwty95.default/extensions/%7Bd634138d-c276-4fc8-924b-40a0ea21d284%7D.xpi!/inline/
200: filename content-length last-modified file-type
201: fonts/ 0 Mon,%2031%20Dec%201979%2023:00:00%20GMT DIRECTORY
201: i18n/ 0 Mon,%2031%20Dec%201979%2023:00:00%20GMT DIRECTORY
201: images/ 0 Mon,%2031%20Dec%201979%2023:00:00%20GMT DIRECTORY
201: injected.js 149720 Thu,%2029%20Nov%201979%2023:00:00%20GMT FILE
201: injected/ 0 Mon,%2031%20Dec%201979%2023:00:00%20GMT DIRECTORY
201: menu/ 0 Mon,%2031%20Dec%201979%2023:00:00%20GMT DIRECTORY
201: notifications/ 0 Mon,%2031%20Dec%201979%2023:00:00%20GMT DIRECTORY
201: save-dialog/ 0 Mon,%2031%20Dec%201979%2023:00:00%20GMT DIRECTORY

kaitlyn

Hi @fiokins! Did you notice something going wrong with 1Password X, or did you happen to check your log and see an error?

Let me know, I'm here to help.

fiokins

I'm a web developer, so I see this every time I have the developer tools open (all day) as the last thing in my console. It's hugely inconvenient as it's a large error that takes up the lower 1/3 of my developer console.

It doesn't seem to affect 1PassX performance, so no big deal I guess.

kaitlyn

@fiokins – I see what you're saying. I wanted to make sure there wasn't an issue that went along with it. I'll let me team know you're seeing a source map error in the console. Thanks for letting us know!

ref: dev/core/core#1089

skoging

The file injected.js has a reference to this missing source map, which causes the warning in Chrome, Firefox, and Edge (chromium).

// inline/injected.js
...
    if (window === window.top) {
        new TopFrameManager();
    }
    else {
        new NestedFrameManager();
    }

}());
//# sourceMappingURL=injected.js.map

The option "Selected context only" will hide this warning, as a work around, but it has some caveats:

• It is not sticky, it has to be selected every time dev tools is opened.
• Other errors/warnings from other contexts are also hidden: API calls to other domains, iframes, etc...

The proper fix for this is fairly straight forward, either include the source map file, or remove the reference to the source map.

The chromium issue has a response marking the problem of "reporting more errors" as WONTFIX. This issue would fall under that category, as the source map is in fact missing, like the warning says.

kaitlyn

Thanks for adding your input, @skoging! I'll pass your report along to my team.

ref: dev/core/core#1089

billtrik

I can verify what @skoging is saying in his comment:

The proper fix for this is fairly straight forward, either include the source map file, or remove the reference to the source map.

That should be a very quick and easy fix for the dev team.

For me it was so annoying that i had to try the other extension you are offering (1password), but i found it lacking the auto-comp.
I have to say seeing this error is less annoying than not having the AutoCompletion popups, but still it is.

Please fix this!

kaitlyn

Thanks, @billtrik! I'll pass your feedback along as well.

ref: dev/core/core#1089