Open Bug 1586760 Opened 5 years ago Updated 2 years ago

Addon Rollbacks remove user installed addons if they were previously enrolled in a addon rollout with a different version of the same addon

Categories

(Firefox :: Normandy Client, defect, P3)

Desktop
All
defect

Tracking

()

Tracking Status
firefox70 --- affected
firefox71 --- affected

People

(Reporter: ppop, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

[Affected Platforms]:

  • All Windows
  • All Mac
  • All Linux

[Affected Versions]:

  • Firefox Nightly 71.0a1, Build ID 20191006214844

[Prerequisites]:

  • Have access to the delivery console.
  • Have an active addon-rollout recipe.
  • Have a profile that can be targeted by the addon-rollout recipe.

[Steps to reproduce]:

  1. Open the browser with the profile from prerequisites.
  2. Navigate to about:addons and remove the rolled-out addon.
  3. Install a different version of the addon with the same ID.
  4. Set-up and save an addon-rollback targeting the previously made addon-rollout.
  5. Restart the browser.
  6. Navigate to about:support and observe the page.

[Expected result]:

  • The user installed addon is displayed on the page.

[Actual result]:

  • The user installed addon is removed by the rollback.

[Notes]:

  • I have attached a screen recording of the issue:

The priority flag is not set for this bug.
:mythmon, could you have a look please?

For more information, please visit auto_nag documentation.

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

Attachment

General

Created:
Updated:
Size: