|
From: | Johannes Marbach |
Subject: | Re: [Bug-gnuzilla] Addons |
Date: | Tue, 1 Oct 2019 21:01:21 +0200 |
I dug into this some more today and noticed this output when running
IceCat from the terminal 1569952665143 addons.xpi WARN Download of https://addons.mozilla.org/firefox/downloads/file/3413998/librifyjs_sumofusorg-0.1.0-an+fx.xpi?src=""> failed: Error: Cannot find id for addon /tmp/tmp-nym.xpi (resource://gre/modules/addons/XPIInstall.jsm:1544:17) JS Stack trace: address@hidden:1544:17 So that indeed confirms that the missing extension ID is the culprit. Some people have also mentioned a similar error message in posts about the expired certificate problem that broke *all* Firefox extensions earlier this year (see https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons-in-firefox/). However, if I'm understanding correctly, this has been fixed in 60.6.3 so IceCat being based on 60.7.0 should not be affected. Indeed, the extension(s) they offered as a temporary workaround in the post linked above did not seem to help in IceCat. This also doesn't seem related because IceCat appears to be setting xpinstall.signatures.required to false by default which should skip the signature check. On 9/30/19 10:01 PM, Johannes Marbach
wrote:
Hi Michael, I'm facing similar issues with my own extensions and I think I've tracked it down to a setting in the extension's manifest. Out of my three extensions, the only one that installs in IceCat from addons.mozilla.org has this in its manifest: "browser_specific_settings": { "gecko": { "id": "...", "strict_min_version": "50.0" } } The other two don't have the ID or minimum version set in their manifest and they fail to install from addons.mozilla.org. I downloaded the XPIs for the extensions you listed and none of them seem to have this settings section either in their manifest. This guy here describes how one could download the extension's XPI, modify the manifest, then have Mozilla sign it for self distribution to finally install it: https://github.com/mozilla/addons/issues/851#issuecomment-480539714 That doesn't seem to be a long-term solution though. :/ Best, Johannes |
pEpkey.asc
Description: application/pgp-keys
[Prev in Thread] | Current Thread | [Next in Thread] |