Error getting purchases updates?

[juampiq6]

So i have almost made subscriptions in my app work, but im only lacking one step: handling old expired subscriptions.
So whenever i test in debug, i get like 12 renewals. But if close the app and stop handling them, then i should get them all in the next app startup. This is not happening and i only get one per app open.
So, is there a way to flush expired purchase event programmatically?
Currently im using the useIAP hook and handling the currentPurchase variable change, which is working if i dont have a lot of expired purchases.
Can someone guide me into this to check if its an Apple server error to be sending just one in debug, but it doesnt happen in TestFlight nor in prod?

[mattwoodage]

@juampiq6 did you solve this? I am seeing the opposite on 3.1.8. If i close my app for a few hours and then open it, each subscription renewal that happened whilst the app was closed calls onPurchaseSuccess. Mine are timed at 9 minutes between renewals.

[juampiq6]

Maybe I missed something but when is onpurchasesucces called? I mean when does the library call it?

[hyochan]

@mattwoodage That’s expected in sandbox: every auto-renewal while the app is closed will arrive as a separate purchase update, so onPurchaseSuccess fires once per renewal when you reopen (your ~9-minute spacing matches sandbox renewal cadence).

What to do

• Finish each renewal: iOS → finishTransaction, Android → acknowledge (subs are non-consumable).

• Add idempotency so you don’t double-grant: persist processed IDs and early-return if seen.

  • iOS: use transactionId (and/or originalTransactionId/webOrderLineItemId)
  • Android: use purchaseToken

• If you prefer not to handle renewals on device, move logic to the server (receipt validation) and use App Store Server Notifications v2 / Google RTDN; the app just finishes the transaction.

[mattwoodage]

I have server notifications now and things are working as expected - although verification doesn't work in sandbox - i'm assuming it will work in prod.

[hyochan]

@juampiq6 You won’t get a “batch replay” of all past renewals. Stores only deliver pending/unfinished transactions as purchase updates. If you’re seeing just one per app launch, it usually means earlier transactions weren’t finished; the store then replays the oldest one each time.

What to do

1. On app startup, call getAvailablePurchases() to load any pending/restore-able transactions.
2. Validate each on your server (source of truth for subscription status).
3. Call finishTransaction() for each to clear the queue.
4. Prefer the hook callback (e.g. onPurchaseSuccess) over polling a single currentPurchase value.

Also note: Sandbox renewal timing/behavior differs from TestFlight/production, so don’t rely on debug renewals to mimic prod.

[juampiq6]

Thanks a lot for this response, you have cleared all my doubts!
I did have notion of the timing for the renewals, but not about how to correctly handle the closed app events.
I've got one more question though. What does the getAvailablePurchases() method return in terms of finished or unfinished tx?