Closed Bug 1858212 Opened 1 year ago Closed 2 months ago

Switch reference-browser AAB signing back to production autograph

Categories

(Release Engineering :: General, task)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gbrown, Assigned: jcristau)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

Currently, for trial purposes, r-b AAB signing is configured for autograph stage. This is my reminder to switch back to production when our testing is complete and the new key is available in production.

Blocks: 1567912
See Also: → 1884210
Depends on: 1884210
See Also: 1884210
Assignee: gbrown → nobody
Duplicate of this bug: 1916252

Ryan, heads-up that when we rotate the key per https://support.google.com/googleplay/android-developer/answer/9842756#lost there will be a window between when google make the change and when we roll out the switch on our end where we might not be able to upload r-b; not to mention the risk of something going wrong, since we can't easily test this ahead of time.
Is there a preferred timeframe to attempt this, and/or other folks that need to be made aware?

Flags: needinfo?(ryanvm)
Assignee: nobody → jcristau
Status: NEW → ASSIGNED

I don't think that's a particularly big concern as long as we're aware of it when the time comes.

Flags: needinfo?(ryanvm)

I've requested an upload key reset on the play console.

The latest reference-browser nightly aab is signed with the new upload key from autograph prod; it's not yet accepted by the play store, as expected. I'll confirm tomorrow's push works before closing this bug.

Status: ASSIGNED → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: