Closed
Bug 568151
Opened 15 years ago
Closed 15 years ago
New version of addon approved but not ask for upgrade
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
VERIFIED
WORKSFORME
People
(Reporter: ietabplus, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 GTB7.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 GTB7.0
The new version of addon (IE Tab Plus v1.90.20100517) was just approved for public today. But when I opened Firefox, it didn't ask me to upgrade the addon like before. The old one installed in my Firefox is Coral IE Tab v1.85.20100407
I changed addon name from Coral IE Tab to IE Tab Plus in this new version, is that the reason for it to be treated as a new addon so no upgrade prompt are displayed?
Reproducible: Always
Steps to Reproduce:
1. Download and install Coral IE Tab v1.85.20100407 from http://downloads.mozdev.org/coralietab/coral_ie_tab-1.85.20100407-fx-win.xpi
Actual Results:
Open your Firefox and it wont ask you to upgrade it to IE Tab Plus v1.90.20100517
Expected Results:
I hope it can upgrade all Coral IE Tab installations to IE Tab Plus smoothly after the name change.
Comment 1•15 years ago
|
||
moving to Toolkit/addon Manager but this could be an AMO bug
Component: Extension Compatibility → Add-ons Manager
Product: Firefox → Toolkit
QA Contact: extension.compatibility → add-ons.manager
Version: unspecified → 1.9.2 Branch
Comment 2•15 years ago
|
||
Does a manual check work for you? If yes, can you please enable extension logging and attach your extensions.log after such a try? When was it working for you directly after installation?
Looks like the problem is caused by the delay of propagation of new approved addons on AMO. So it's not a bug.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Comment 4•15 years ago
|
||
Thanks for rechecking. Marking as WFM then.
Status: RESOLVED → VERIFIED
Resolution: FIXED → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•