Closed Bug 1740792 Opened 4 years ago Closed 3 years ago

Two error conditions are missing text

Categories

(Toolkit :: Add-ons Manager, defect, P2)

defect

Tracking

()

RESOLVED FIXED
101 Branch
Tracking Status
firefox101 --- fixed

People

(Reporter: mixedpuppy, Assigned: robwu)

Details

Attachments

(1 file)

Severity: -- → S3
Priority: -- → P2

ERROR_UNEXPECTED_ADDON_TYPE is triggered when a WebExtension is changed to a non-WebExtension. We don't support non-WebExtensions, the only entries are old installations, so this scenario is not possible any more.

ERROR_INCORRECT_ID is when the addon ID changes during an upgrade. That shouldn't happen, and it's an error of the add-on distributor.
https://searchfox.org/mozilla-central/rev/3c8a7970944daaf917b547dffc0790bcd37cadc1/toolkit/mozapps/extensions/internal/XPIInstall.jsm#1535-1550

Only the last one may be worth translating.

ERROR_UNEXPECTED_ADDON_TYPE will be re-used by my patch to bug 1750565.

While testing that manually, I realized that these errors (ERROR_UNEXPECTED_ADDON_TYPE and ERROR_INCORRECT_ID) only happen as a part of updates (automatic or manual updates), and immediately interrupt the update flow without UI (e.g. doorhangers). The error is dumped to the console.

The logic referenced in this report is about doorhangers that appear when a non-update XPI installation is triggered.
When someone attempts to (re-)install a XPI, then that doesn't count as an update, and the install flow does not account for the existing add-on (i.e it's not an update, and the branches that yields the two error codes are not taken).

Assignee: nobody → rob
Status: NEW → ASSIGNED
Pushed by rob@robwu.nl: https://hg.mozilla.org/integration/autoland/rev/f234874664b4 Replace TODO with explanatory comment r=rpl DONTBUILD
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 101 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: