Restore and Account Recovery

Start with identity

If your product has accounts, the cleanest recovery path is a stable appUserId on every install and every device. That reduces your need to rely on restore flows as the primary identity mechanism.

Use the right recovery API

Use restore when the customer explicitly asks to recover purchases.
Use quiet sync when you need a silent reconciliation step.
Use receipt queue drain when you intentionally need to flush retryable receipt work and refresh state.

User-facing restore button

let info = try await AppActor.shared.restorePurchases()
if info.hasActiveEntitlement("premium") {
    showPremiumHome()
} else {
    showNoPurchasesFoundMessage()
}

val info = AppActor.shared.restorePurchases()
if (info.hasActiveEntitlement("premium")) {
    showPremiumHome()
} else {
    showNoPurchasesFoundMessage()
}

final info = await AppActor.instance.restorePurchases();
if (info.hasActiveEntitlement('premium')) {
  showPremiumHome();
} else {
  showNoPurchasesFoundMessage();
}

const info = await AppActor.instance.restorePurchases();
if (info.hasActiveEntitlement('premium')) {
  showPremiumHome();
} else {
  showNoPurchasesFoundMessage();
}

Do not call restore automatically on every startup. Put it behind an explicit user action such as a settings-screen “Restore purchases” button.

Scenario matrix

Scenario	Recommended flow
Reinstall with same app account	Configure with the stable `appUserId`, then call `getCustomerInfo()`.
Customer taps restore	Call `restorePurchases()` and check customer info.
Silent login reconciliation	Call `syncPurchases()` only when you intentionally need store reconciliation.
Receipt was queued locally for retry	Call `drainReceiptQueueAndRefreshCustomer()` from support/debug/recovery UI.
Consumable/token product	Wait for backend receipt acceptance or refreshed customer/token state before granting final credit.

Reinstall behavior

Anonymous users can end up with a new local identity after reinstall. If your product needs stronger continuity, prefer:

sign the user into your app account
configure AppActor with the same stable appUserId
run the appropriate recovery flow only if customer state still needs reconciliation

Consumables and credits

For consumables, tokens, and backend-granted credits, wait for backend receipt acceptance rather than assuming every local purchase callback represents a final server-side grant.

Overview

Get Started

Testing and Go Live

Features

Remote Config

Experiments

Platform Resources

AI-Ready

Restore and Account Recovery

Start with identity

Use the right recovery API

User-facing restore button

Scenario matrix

Reinstall behavior

Consumables and credits

​Start with identity

​Use the right recovery API

​User-facing restore button

​Scenario matrix

​Reinstall behavior

​Consumables and credits

Start with identity

Use the right recovery API

User-facing restore button

Scenario matrix

Reinstall behavior

Consumables and credits