Closed
Bug 1490771
Opened 8 years ago
Closed 8 years ago
Add-on that has been working for months is now disabled in Firefox 62.
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: AllworxAdvAppDev, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36
Steps to reproduce:
- Install the add-on (side-loaded) in Firefox 61
- VERIFY: The add-on is loaded, and runs properly
- Upgrade Firefox to version 62
NOTE: I have attached a Windows installer that performs the side-loading of the add-on.
cf: https://discourse.mozilla.org/t/add-on-not-supported-as-of-firefox-62/31711
Actual results:
The add-on is disabled in version 62 with the error message "<name> could not be verified for use in Firefox and has been disabled."
Expected results:
The add-on is loaded, and runs properly.
| Reporter | ||
Comment 1•8 years ago
|
||
The signed add-on
Updated•8 years ago
|
Component: Untriaged → Add-ons Manager
Product: Firefox → Toolkit
| Reporter | ||
Comment 2•8 years ago
|
||
At this point, I am relatively confident that side-loading is the issue. I was able to publish my add-on to AMO, and it loads into Firefox 62 just fine and runs correctly:
https://addons.mozilla.org/en-US/firefox/addon/allworx-interact-sync/
However, if I download that specific xpi from AMO, unzip it and try to side-load it into Firefox 62, then I get the " ... could not be verified for use in Firefox ... " message.
Comment 3•8 years ago
|
||
(In reply to AllworxAdvAppDev from comment #2)
> However, if I download that specific xpi from AMO, unzip it and try to
> side-load it into Firefox 62, then I get the " ... could not be verified for
> use in Firefox ... " message.
You should not unzip it, unpacked extensions are not supported:
https://blog.mozilla.org/addons/2018/02/22/removing-support-unpacked-extensions/
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
| Reporter | ||
Comment 4•8 years ago
|
||
Thank you. I missed this blog post. I now understand what needs to be done. I appreciate your help and patience.
You need to log in
before you can comment on or make changes to this bug.
Description
•