Closed Bug 1900911 Opened 9 months ago Closed 9 months ago

Clean up reference to now non-existant updateManager.readyUpdate use

Categories

(Toolkit :: Application Update, defect)

defect

Tracking

()

RESOLVED FIXED
128 Branch
Tracking Status
firefox-esr115 --- unaffected
firefox126 --- unaffected
firefox127 --- unaffected
firefox128 --- fixed

People

(Reporter: bytesized, Assigned: bytesized)

References

(Regression)

Details

(Keywords: regression, Whiteboard: [fidedi-ope])

Attachments

(1 file)

Bug 1875502 replaced UpdateManager.readyUpdate with an asynchronous version, UpdateManager.getReadyUpdate as well as a more specialized version: UpdateManager.updateInstalledAtStartup. But I seem to have missed a spot where we still use the old, now nonexistent value. I believe this is causing many update pings to not be sent so we should fix this quickly.

Set release status flags based on info from the regressing bug 1875502

Blocks: 1901143

This patch doesn't include testing. This is in large part because I need this to land quickly so that it can be uplifted, and in small part because I believe that testing can be added fairly trivially to a test that will be added in Bug 1889785, right after the soft freeze is over.

Pushed by rsteuber@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5416c2138ff4 Fix reference to now non-existant updateManager.readyUpdate r=nalexander,firefox-desktop-core-reviewers ,Gijs
Status: NEW → RESOLVED
Closed: 9 months ago
Resolution: --- → FIXED
Target Milestone: --- → 128 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: