Handle sync recovery basic scenario

[MiSikora]

Task/Issue URL: https://app.asana.com/1/137249556945/project/1216103556496795/task/1217050743419836?focus=true
Tech Design URL (if applicable): https://app.asana.com/1/137249556945/project/1216103556496795/task/1216509582049467?focus=true
API Proposals URL(s) (if applicable): N/A

Description

Wires up the "Recover Synced Data" flow in the simplified Sync Settings screen, so users can restore their synced data with a recovery code, and adds a confirmation screen shown when recovery completes.

Recovery flow:

• Tapping "Recover Synced Data" in the disabled state now requires device authentication and then opens a new screen explaining that the recovery code from the original setup is needed.
• Tapping "Recover Synced Data" on that screen opens the code scanner in recovery mode. The "Show QR Code" button is hidden there, since showing a code cannot recover data. Manual code entry keeps working.
• While the code is being processed, the connecting screen shows the headline "Recovering data" instead of the pairing headline.
• After a successful recovery the acknowledgement animation now plays before the flow completes.

Cleanup:

• Commands with no equivalent in the simplified flow (AskRemoveDevice, AskSetupSyncDeepLink, AskTurnOffSync, ShowRecoveryCode) are now explicit no-ops instead of TODO logs.
• The unused ShowDeviceConnected command is removed from the existing Sync Settings screen.

Steps to test this PR

Note

Prepare yourself a recovery PDF before executing these tests.

Recover synced data with a recovery code

• On a device with sync disabled, open Sync Dev Settings.
• Tap "Launch Sync Settings V2".
• Tap "Recover Synced Data".
• Complete the device authentication prompt.
• Verify the "Recover your synced data" screen opens.
• Tap "Recover Synced Data".
• Verify the scanner opens without a "Show QR Code" button.
• Scan a recovery code QR code.
• Verify the connecting screen shows the headline "Recovering data".
• Verify the acknowledgement animation plays.
• Verify the "Sync & Backup enabled" screen opens.
• Tap "Done".
• Verify the confirmation screen with a recovery code opens.

Scan a pairing code from the recovery flow

• With sync disabled, tap "Recover Synced Data" in Sync Settings.
• Tap "Recover Synced Data" on the recovery screen.
• Scan the QR code shown on another device's "Sync With Another Device" screen.
• Complete the pairing confirmation dialogs.
• Verify the confirmation screen with a recovery code opens.

Scan a recovery code from the pairing flow

• With sync disabled, tap "Sync With Another Device" in Sync Settings.
• Scan a recovery code QR code.
• Verify the confirmation screen with a recovery code opens.

UI changes

Recover Synced Data	Recovering data

---

Note

Medium Risk
Touches account recovery and pairing completion paths across multiple activities; incorrect OriginalFlow handling could skip or wrongly show the recovery-code step after login.

Overview
Adds the Recover Synced Data path to simplified Sync Settings v2: a new intro screen, scanner behavior in recovery mode, and completion routing driven by OriginalFlow instead of pairing role/method.

Recover flow: IntroRecoverSyncData in v2 SyncActivity now opens RecoverSyncedDataActivity (after auth), which launches ReadSyncCodeContract with OriginalFlow.RECOVER_SYNCED_DATA. In recovery mode, Show QR Code is hidden on the scanner; the exchange screen headline switches to Recovering data; v2 recovery login triggers the acknowledgement animation before finishing.

Result model: SyncPairingResult.Success now carries originalFlow (SYNC_THIS_DEVICE, SYNC_WITH_ANOTHER, RECOVER_SYNCED_DATA) instead of Role and PairingMethod. That value is passed through DisplayQrCode / ExchangeSyncCode / ReadSyncCode contracts and intents so handlePairingResult can show the recovery-code screen for sync-this-device and recover flows, but not when adding another device.

Cleanup: Removes ShowDeviceConnected / legacy SETUP_COMPLETE handling from v1 SyncActivity. Several v2 commands that have no simplified UI are explicit no-ops instead of TODO logs.

^{Reviewed by Cursor Bugbot for commit 9b276ef. Bugbot is set up for automated code reviews on this repo. Configure here.}

[MiSikora]

• Replace ScrollView with NestedScrollView in sync settings #9424
• Simplified sync translations #9414
• Parameterize sync pixels tests #9413
• Apply correct edge to edge handling in simplified sync #9412
• Add simplified sync pixels #9401
• Clean up sync code before integrating pixels #9386
• Avoid signing out of a device when renaming it #9374
• Handle simplified sync deep linking #9373
• Handle restore on reinstall sync scenario #9368
• Simplified sync UI updates #9363
• Handle v1 exchange sync codes #9362
• Handle sync recovery basic scenario #9356 👈 (View in Graphite)
• Add syncing with another device logic and navigation #9343
• Add generic handling of v1 sync errors #9337
• Add sync with another device UI #9334
• Detect scanned QR sync codes #9333
• Handle sync code pasting #9332
• Refactor simplified sync class names #9329
• Handle sync logic on the displayed QR code page #9328
• Display sync QR code in simplified sync #9321
• Make remove device dialog destructive #9317
• Mitigate sync settings UI race condtions #9316
• develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 40915f5. Configure here.}

[MiSikora]

Merge activity

• Aug 4, 12:40 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Aug 4, 1:11 PM UTC: The Graphite merge of this pull request was cancelled.
• Aug 4, 1:39 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Aug 4, 1:41 PM UTC: Graphite rebased this pull request as part of a merge.
• Aug 4, 1:53 PM UTC: @MiSikora merged this pull request with Graphite.