App Store / Google Play · 清单验收 · 不承诺过审Telegram @hagee66

上架通

GOEE LISTING LEDGER

№ ENgoee.cc
账号归你 · 邀请协作


2026-02-20

Restore purchases UX: entry, copy, and review demo

Where to put Restore for subs and non-consumables, what to say, how reviewers reach it. Telegram @hagee66.

This guide · Guide library · Apple listing · Google listing · Both stores · Telegram @hagee66

Restore Purchases is not a power-user Easter egg—it is standard for non-consumables and subscriptions. Reviewers on new devices, reinstalls, and sandbox re-entry look for it per your notes; missing or dead buttons land in payment or Guideline rejections alongside price disclosure.

Goee (goee.cc) ties restore to IAP notes SKU table and sandbox paths on one acceptance sheet. No single button placement standard, but users must recover paid entitlements—per Apple and Google review guidance. No approval promise.

What this guide solves

  • Restore buried at bottom of About; notes cite path—still “not found.”
  • Toast “success” but VIP UI unchanged—looks broken.
  • Subs and lifetime in one group; restore handles only one type.
  • Login required but sandbox not bound to your server account.
  • Android Play query only—no user-facing “restore” narrative.
  • Release notes claim “added restore” but entry still invisible.

Unify placement, copy, feedback, and notes into one demonstrable path.

Who should read

Role Use
iOS/Android client StoreKit / Play Billing restore + UI refresh
Product Placement vs buy again
Listing Review notes + sandbox
IAP rejection teams Fix restore before resubmit

Consumables (coins) usually no restore—if sub misconfigured as consumable, fix type in IAP notes first.

Core practice

1. What must restore

  • Auto-renewing subs: new device/reinstall same store account → active sub.
  • Non-consumables (lifetime, remove ads): restore—no repurchase for same capability.
  • Consumables: no restore substitute for buy again—don’t label rebuy as Restore.

Types per Connect/Console; client entitlements match backend.

2. Where to put entry

Visible near purchase or account—findable in minutes.

Place Fit Note
Paywall same screen Strong Reviewer can restore without buying
Settings → subscription/member Good Short path for notes
Profile header OK Not hidden in hamburger
About footer Weak Often “not prominent”

Play: clear equivalent (“Restore purchases/subscription”); notes include exact label.

3. Copy and states

  • Plain meaning: “Restore purchases” / “Restore subscription”—not vague “Sync.”
  • Loading while running—block double tap.
  • Success: VIP/ad removal updates immediately—not toast-only.
  • No purchases: explain wrong account / other platform—no scare tactics.
  • Failure: network/store guidance; log codes for support.

4. Account coupling

If entitlements bind app account + receipt, fix order in product and notes: login first or restore first. Reviewers test fresh install—prefer store-only restore, optional in-app bind. Login demo notes.

5. Review script

  1. Sandbox buy sub or non-consumable.
  2. Delete app / new device.
  3. Open app → notes path → Restore.
  4. VIP without repaying.

Notes: sandbox account, product name, path, visible UI after (e.g. “VIP until date in Settings”).

6. Cross-platform story

If iOS/Android differ, store copy states scope; test each side. No “all-platform member” on one side only.

7. Play billing details

Query APIs evolve—Google official docs. Log USER_CANCELED, timeout, missing product, expired sub by build for support.

Grace/billing retry: show “payment pending” honestly—not fake VIP.

8. Plan changes and promos

Restore reflects current entitlement—not historical max tier. Don’t promise “restore = highest forever.” Server must refresh receipt after restore. Promos: offer codes; family: family sharing IAP.

Submit-week smoke: buy → kill app → restore → uninstall → restore again.

Copy-paste templates

[Restore acceptance]
Platform: iOS / Android
Product IDs and types:
Sandbox/license account:
Build where purchased:
Restore entry (button label):
UI before restore (paywall?):
Loading state: Y/N
Success UI change:
Empty state copy:
Login coupled: Y/N (order)
Notes synced: Y/N

Review note snippet

[Restore]
Sandbox XXX purchased "Monthly Member".
Reinstall: App → Settings → Member → "Restore Purchases"
Expected: no repurchase; home shows Member badge; expiry matches store.
If login first: test user … / pass …

Common mistakes

  1. iOS Restore only—Android none.
  2. Local cache only—no server receipt validation.
  3. Gesture/dev menu hide.
  4. Expired sub still VIP.
  5. Notes say Settings but control buried third level.
  6. New entry same build not bumped.
  7. Family/offer codes not retested.

FAQ

Button size vs Buy?
No pixels—must be noticeable; same screen as purchase safest.

Restore before login?
If receipt-only entitlements, prefer no-login restore; if login required—notes + pre-purchase disclosure.

“No purchases” but user paid?
Sandbox vs prod, SKU change, wrong Apple ID—support script checks ID + SKU.

Play silent background query only?
Users and review need visible control.

3.1.1 + restore mentioned?
IAP notes fix buy + price first; both in resubmit notes.

Next steps

Related reading

Back to guide library · Telegram @hagee66