Repository navigation
Restore retained wallet keys from encrypted Google Drive backups - #479
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.
Wallets blocked by
missing_wallet_secretcan now restore an existing encrypted Google Drive backup directly from the recovery screen. The reader uses bounded, exact-file reads and rejects ambiguous matches; every supplied phrase, seed or encrypted JSON credential must prove the retained SORA identity before an absent credential is added. Existing account records, credentials and recovery state are preserved until full startup verification succeeds. Mnemonic recovery enables Taira through the existing derivation policy; seed-only and JSON-only accounts retain their existing SORA2-only policy.The screen distinguishes missing backups, wrong passwords, identity mismatches and protected-storage failures. The password stays on the phone. Validation passed: 274 canonical Release wallet tests, zero failures/skips, unchanged hashes for all 6,085 tracked files, 7 focused recovery tests, 16 collector tests, and 8 publication-contract tests. The exact tested runtime patch is integrated into the primary checkout with its index and unrelated work preserved.
Build 2026091303 is pinned to runtime
204ee5a7bbc58fc7d3b88d429bfc2198ad79e2faand publication6f7625b3d40b19b06166fa418ba2359731e1b2ef. The verified archive/IPA was accepted by Apple at 2026-09-13T14:16:08Z, delivery2d4ab467-a8bf-49d4-9143-06153e90b6f8, with no package-upload errors and nine vendor dSYM symbol warnings. Processing is complete and the build is Ready to Submit, with only the two internal App Store Connect Users attached; external groups and beta review are not yet submitted, and public-link availability is unconfirmed.The build is installed in place and the retained account identity is unchanged. The reporting phone still has
database_migration / missing_wallet_secret. The attempted Drive recovery found no matching backup and did not reach the password stage; a complete metadata-only listing confirmed the currently signed-in account’s SORA app-data space contains zero files or folders. Another account may hold a backup, but this is unproven; the recovery flow currently reuses the existing Google session, and an explicit account-choice correction is under development. Actual wallet recovery and the timing or cause of credential unavailability remain unproven.