Sync Recovery

Safety before taking action

Stop making changes on every synced device until the recovery path is chosen. Keep at least one unlocked device or recent Document Vault packet backup available before any destructive recovery step. Deleting app data, switching providers, or replacing local state can remove local-only changes if no current backup exists.

Common sync recovery paths

• Local-only expected state: export a packet backup from the good device, then import it on the affected device only after confirming replacement is safe.
• One device good, provider stale: pause changes on other devices, export a backup from the good device, then use the app's provider migration or replace-provider path when available.
• Provider good, one device stale: keep the stale device from making changes, confirm the provider account, then use the app's refresh, replace-local, or reconnect path when available.
• Missing assets or hash mismatch: stop sync, preserve local state, collect the redacted error label and build, and contact support before deleting or reconnecting.

Provider notes

For iCloud, confirm the intended Apple ID, iCloud availability, quota, and account restrictions. For Google Drive, confirm the intended Google account and app-data scope. Do not manually edit CloudKit records, Drive app-data files, provider metadata, tombstones, or recovery snapshots.

Need help?

Use Document Vault support and include the app build, platform, active provider, redacted sync state label, whether another device has the expected data, and whether a packet backup exists.