Repository navigation
Let wallet recovery choose a different Google backup account - #480
Draft
takemiyamakoto wants to merge 2 commits into
Draft
takemiyamakoto wants to merge 2 commits into
takemiyamakoto wants to merge 2 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Recovery retries now open Google’s interactive account selection even when SORA already has a signed-in Google account. Previously, a missing backup could leave every retry querying that same account. The reader binds the newly selected account only after authorization succeeds, issues no Drive reads after cancellation or authorization failure, and shows distinct missing-backup and sign-in headings.
The change preserves the existing bounded backup reads, identity verification, credential restoration and wallet migration behavior. It does not establish that the reporting wallet has recovered; the observed signed-in account returned a complete empty SORA backup inventory.
Validation passed: 274 Release wallet tests, zero failures or skips, unchanged hashes for all 6,085 tracked files, and eight publication-contract tests. The existing reader test covers an empty first account, canceled second attempt with no extra Drive query, and a third authorization that reads the exact backup. The exact tested four-file runtime patch is integrated into the primary checkout with unrelated work and the index preserved.
Build 2026091304 is pinned to runtime
a472679a10beb1cc71468bcf25d7f57ac541c744and publicationf38dcd3002aeccd4d21f78b87fe8c7d5ee116ca6. Its signed native archive passed signature and runtime checks. It has not been uploaded or installed; device installation awaits an unlocked phone. A successor is being prepared to address a separately found delete-before-upload risk and missing first-backup completion path before wider distribution.