Duplicate Purchase can't be restored, no new purchases can be made. User stuck.

[SethArchambault]

Now that we have error messages when duplicate purchases are detected, I can show an error message along with a "Restore Purchases" button for those users. However, there seems to be no way to process the duplicate purchase. getAvailablePurchases, which handles purchases that can be restored, does not include these duplicate purchases, so it seems that even though we can now detect that a purchase is a duplicate, we can't find the duplicate or do anything with it.

The error message seems to indicate that we should use getAvailablePurchases, but that doesn't work (I can't use restorePurchase, because I need to send the the purchaseToken to the server for validation)

This occurs when I'm testing just now in Xcode, but I've also seen it when testing on Testflight - we can't go live with this issue as it would put users into a situation where they can't go any further with the app. Thanks!

[hyochan]

Thanks for reporting this @SethArchambault. This is a known edge case with iOS StoreKit when duplicate purchases are detected.

The duplicate purchase detection was added to prevent users from being charged twice, but you're right that the current recovery path is incomplete — getAvailablePurchases only returns the latest transaction per product, so if a purchase is flagged as duplicate, it may not appear there.

Workaround for now:

1. When you catch the duplicate purchase error, you can call clearTransactionIOS() to finish the pending transaction on the native side, which should unblock the user from making new purchases.
2. 2. For the stuck transaction itself, try calling getAvailablePurchases() after clearing — in most cases the original (non-duplicate) transaction should still be available for server-side validation.
      Regarding the root cause:

The issue is that when StoreKit detects a duplicate, the transaction enters an unfinished state but isn't exposed through the available purchases API. I'll look into whether we should surface the purchaseToken / transactionId from the error callback itself so you can still validate it server-side.

Could you share which version of react-native-iap you're using and whether this is a subscription or consumable product? That will help me narrow down the fix.

I'll keep this open and investigate further.

[SethArchambault]

@hyochan Thanks for the quick response - I'll try that clearing suggestion.

This is for react-native-iap 14.7.19, with a subscription.
Thanks!