Add-on does not get update if it's maxVersion is lower than the current appVersion despite default to compatible

RESOLVED FIXED

Status

addons.mozilla.org Graveyard
API
RESOLVED FIXED
6 years ago
2 years ago

People

(Reporter: TheOne, Assigned: robhudson)

Tracking

Details

(Reporter)

Description

6 years ago
I'm running Firefox Aurora 12.0a2 with the add-on Better Privacy (v 1.67).
When I do an update search for this add-on, Firefox sends the following request:

LOG addons.updates: Requesting 
https://versioncheck.addons.mozilla.org/update/VersionCheck.php?reqVersion=2&id={d40f5e7b-d2cf-4856-b441-cc613eeffbe3}&version=1.67&maxAppVersion=10.*&status=userDisabled,incompatible&appID={ec8030f7-c20a-464f-9b0e-13a3a9e97384}&appVersion=12.0a2&appOS=WINNT&appABI=x86-msvc&locale=en-US&currentAppVersion=12.0a2&updateType=97&compatMode=normal

AMO answers that the most current version is 1.66 (no idea why).
Shouldn't it instead return the most current version (v1.68) despite that that version is compatible only to 11.* because of default-to-compatible?
(Assignee)

Comment 1

6 years ago
This is an interesting case. I dug around and it looks like version 1.67 got blacklisted in our compatibility overrides. But then our precomputed table of blacklisted versions is listing version 1.68. I'll investigate further to see why that might have happened, but this would be the reason why it's not showing up in the above query.
Assignee: nobody → chudson
(Assignee)

Comment 2

6 years ago
Added management command to rebuild our denormalized table:
https://github.com/mozilla/zamboni/commit/a9a5c2b 

Will run today and close if fixed.
(Assignee)

Comment 3

6 years ago
That looks like it fixed it.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.