1627292 - Can't install scroll extension from firstlook.firefox.com

Status: NEW

(Toolkit :: Add-ons Manager, defect, P3)

Description

[Andrew Swan [:aswan]]

+++ This bug was initially created as a clone of Bug #1625785 +++

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:76.0) Gecko/20100101 Firefox/76.0

Steps to reproduce:

1. Go to https://scroll.com/ and click on the Setup tab at the top right hand corner.
2. Then scroll to the "Get the Add-on" button and click it.
3. You'll be prompted with the "Allow scroll.com to to install an add-on?" click "Continue to Installation"

Actual results:

I get prompted with an error "The add-on could not be downloaded due to a connection failure"

Expected results:

The add-on should've been installed.

Comment 1

[Andrew Swan [:aswan]]

This was originally reported in bug 1625785, that bug then veered off into an issue with the certificate viewer, but https://bugzilla.mozilla.org/show_bug.cgi?id=1625785#c16 reports that installation is still failing.
Chris, thanks for all your help so far. In the environment in which you reported that comment (ie, FPN disabled), can you try installing the extension, then open the Browser Console (https://developer.mozilla.org/en-US/docs/Tools/Browser_Console) and paste any messages that appear there into a comment here?

Comment 2

[chris.cushman]

Attachment: ErrorsOnConsoleOnFirstLook.png

Thank you for helping as well. Here are the errors I get from this page:

This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. index.html
Content Security Policy: The page’s settings blocked the loading of a resource at inline (“style-src”). 2 index.html
Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). 2 utils.js:35:9
Content Security Policy: The page’s settings blocked the loading of a resource at inline (“style-src”). index.js:2541:22
Content Security Policy: The page’s settings blocked the loading of a resource at inline (“style-src”). index.js:2545:22
Content Security Policy: The page’s settings blocked the loading of a resource at inline (“style-src”). index.js:2549:22
Content Security Policy: The page’s settings blocked the loading of a resource at inline (“style-src”). index.js:2558:22
Content Security Policy: The page’s settings blocked the loading of a resource at inline (“style-src”). index.js:2574:22
Content Security Policy: The page’s settings blocked the loading of a resource at inline (“style-src”). index.js:2578:22
Content Security Policy: The page’s settings blocked the loading of a resource at inline (“style-src”). index.js:1920:35

Comment 3

[Andrew Swan [:aswan]]

The names here are confusing but that's the regular web console. The Browser Console shows a different set of errors, you can see instructions for opening it at the link in comment 1. Can you paste an errors from the Browser Console during the time you're trying to install the scroll extension?

Comment 4

[chris.cushman]

Attachment: ErrorsInTheConsoleWindow.png

Sorry about that, here is the errors from the Browser Console:

Secure connection established without certificate. ThreadSafeDevToolsUtils.js:90:13
reportException resource://devtools/shared/ThreadSafeDevToolsUtils.js:90
parseCertificateInfo resource://devtools/shared/webconsole/network-helper.js:730
parseSecurityInfo resource://devtools/shared/webconsole/network-helper.js:648
_getSecurityInfo resource://devtools/server/actors/network-monitor/network-response-listener.js:331
makeInfallible resource://devtools/shared/ThreadSafeDevToolsUtils.js:111
onStartRequest resource://devtools/server/actors/network-monitor/network-response-listener.js:225
1586014579610 addons.xpi WARN Download of https://firstlook.firefox.com/betterweb/fbw-ext.xpi failed: [Exception... "Certificate issuer is not built-in." nsresult: "0x80004004 (NS_ERROR_ABORT)" location: "JS frame :: resource://gre/modules/CertUtils.jsm :: checkCert :: line 179" data: no] Stack trace: checkCert()@resource://gre/modules/CertUtils.jsm:179
onStopRequest()@resource://gre/modules/addons/XPIInstall.jsm:2417

Comment 5

[chris.cushman]

I googled the "Certificate issuer is not built-in." error and found this: https://discourse.mozilla.org/t/add-on-update-certificate-issuer-is-not-built-in/19457/2 it said to set xpinstall.signatures.required to true in about:config but it didn't work.

Comment 6

[Andrew Swan [:aswan]]

The "Secure connection established without certificate" errors are coming from devtools, the error that's causing the extension install failure is this one:

1586014579610 addons.xpi WARN Download of https://firstlook.firefox.com/betterweb/fbw-ext.xpi failed: [Exception... "Certificate issuer is not built-in." nsresult: "0x80004004 (NS_ERROR_ABORT)" location: "JS frame :: resource://gre/modules/CertUtils.jsm :: checkCert :: line 179" data: no] Stack trace: checkCert()@resource://gre/modules/CertUtils.jsm:179

But based on https://bugzilla.mozilla.org/show_bug.cgi?id=1625785#c16 that doesn't make sense.
I suspect these are all probably linked to the same underlying problem as bug 1625785, lets wait and see what the outcome is there.

Comment 7

[chris.cushman]

Attachment: NewProfileDownloadedScroll.png

So when trying to get a log, I created a new profile and logged my try of downloading the extension. It downloaded correctly. So I guess its something with my profile that is causing it. How could I narrow this down further?

Comment 8

[Andrew Swan [:aswan]]

This won't get us to the bottom of the issue, but we could bisect the problem a little bit if you try your regular profile but in safe mode?
https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems#w_start-firefox-in-safe-mode

Comment 9

[chris.cushman]

Sorry for the long response on this. I need to set the needs more info tag to me so I'm writing this comment.

Comment 10

[BugBot [:suhaib / :marco/ :calixte]]

Clear a needinfo that is pending on an inactive user.

Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.

For more information, please visit BugBot documentation.