Report from slack:
I sync'ed my FxA account with Fenix on my Android phone lately. My addons are synchronized (mostly to use the same on my different laptops). Now I have PrivacyBadger enabled in Fenix, although it is not supposed to be compatible/available.



When investigating we found that, after a recent change, we're now triggering updates for unsupported add-ons as well. Not sure if that can cause this, but will put up a fix.
Other report of this in Fenix: https://github.com/mozilla-mobile/fenix/issues/9145
In mozilla-mobile/fenix#9145, we know it was not migration-related. Add-ons were disabled correctly during migration and somehow got enabled prematurely. We still need to confirm if the temporary bug we had that triggered updates for those add-ons is the cause before closing this.
Hi @csadilek,
Even if this was a bug it was a good test to see which extensions were working 馃槃
Cheers 馃檪
Changes landed in beta and nightly and A-C versions upgraded.
Note to QA to reproduce / verify this:
--> Up until this point, the steps were already verified in the past and have always worked
Without the fix, the add-on is in an inconsistent state i.e. it's active and might send browser actions, but shows as unsupported in the add-on manager.
With the fix, the add-on is still correctly disabled and marked as unsupported after upgrading to a new major Gecko version.
Hi! I could reproduce this on Pixel 2 (Android 9) and Huawei P9 Lite (Android 7) following the steps:
Using the latest Fennec Nightly Migration build from 3/23 GV 76, the unsupported add-ons are not active and are not displayed in the menu.
Note: The issue is still reproducible when updating from GV 76 to the latest GV 76 build. @csadilek Is this expected? Thanks!
Note: The issue is still reproducible when updating from GV 76 to the latest GV 76 build. @csadilek Is this expected? Thanks!
Thank you for verifying! We talked about this offline. This is as expected, as between steps 3. and 4. using the unfixed GV 76, the embedderDisabled state is lost, so upgrading to the latest GV 76 (with the fix) won't help at this point. This is not an issue though as it will be fixed for upgrades going forward.
Since this is verified as fixed in the previous comment, I will move this to Done. Thanks!
Most helpful comment
In mozilla-mobile/fenix#9145, we know it was not migration-related. Add-ons were disabled correctly during migration and somehow got enabled prematurely. We still need to confirm if the temporary bug we had that triggered updates for those add-ons is the cause before closing this.