I have renewing subscriptions working in Test Flight and wanted to validate a few things to make sure things will work the same in production before I go live.
When a user purchases a subscription, I validate the receipt, finish the transaction and then save the original receipt to a database for that user.
On app startup, I get the receipt from the database, validate it again and check the expiration date. If it's not expired I let them in.
This all works even when the subscription auto-renews. When I pull the receipt from my database and validate it, the new subscription end date is there after an auto-renew and it all looks great! It's all working with the original receipt from the original purchase.
Is it supposed to work this way? I thought each renewal of a subscription had a new receipt.
I just want to make sure it works the same in production, otherwise all my subscriptions will stop working after the first renewal.
If it matters, I am using React Native and the dooboolab iap library.
When a user purchases a subscription, I validate the receipt, finish the transaction and then save the original receipt to a database for that user.
On app startup, I get the receipt from the database, validate it again and check the expiration date. If it's not expired I let them in.
This all works even when the subscription auto-renews. When I pull the receipt from my database and validate it, the new subscription end date is there after an auto-renew and it all looks great! It's all working with the original receipt from the original purchase.
Is it supposed to work this way? I thought each renewal of a subscription had a new receipt.
I just want to make sure it works the same in production, otherwise all my subscriptions will stop working after the first renewal.
If it matters, I am using React Native and the dooboolab iap library.