Open Bug 1562573 Opened 5 years ago Updated 2 years ago

Updates on beta channel should trigger updates of distribution extensions

Categories

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

69 Branch
enhancement

Tracking

()

Tracking Status
firefox69 --- affected

People

(Reporter: darktrojan, Unassigned)

References

Details

Currently, Services.appinfo.version is used to determine whether an application update has occurred, and consequently whether to update distribution extensions. Services.appinfo.version doesn't include the beta version number, and so a user on a beta channel does not get updates to distribution extensions beyond the first update time they update to that version number.

I propose using AppConstants.MOZ_APP_VERSION_DISPLAY instead, which does include the beta version number. I'm willing to write the patch if such a change is acceptable.

Let's NI someone here ;-)

Flags: needinfo?(aswan)

I … did. What happened to it?!

There are a bunch of other things that we do based on the app version changing that I'd prefer to avoid running unnecessarily in beta.
Distribution addons generally are a pain since we do installs/upgrades/etc of them synchronously during startup.
What are you using distribution addons for? Maybe we could figure out a different way to solve whatever problem you're facing.

Flags: needinfo?(aswan)

Our calendar component Lightning is a distribution add-on.

Flags: needinfo?(geoff)
Priority: -- → P3

What am I NI'ed for? Jorg answered the question.

Flags: needinfo?(geoff)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.