I’m attempting to determine a users Subscription monthly window by using https://api.revenuecat.com/v2/projects/{project_id}/customers/{customer_id}/subscriptions current_period_starts_at & current_period_ends_at in conjunction with gives_access & status. However I have seen this data become corrupted in the Test Store where a subscription never gets updated with Expired status or gives_access false. Furthermore this corrupted sub data shows active entitlements forever. This means multiple subscriptions in the array will appear active at the same time even thought one or more are in a corrupted state.
Is this just a known issue in Test Store or should I protect myself by ignoring Gives Access and Status If the current_period_ends_at is exceed? Is there a better way to determine period start and end without the complexity of retrieving all subscription history?
Any thoughts or input would be greatly appreciated.
Issues with a users Subscription data corruption from v2 api
+2Best answer by kaitlin
Hi
This is a test store specific issue you’ve run into (or rather, a sandbox issue in general). The gives_access flag remains true as these test transactions are not passively refreshed as production receipts are, meaning the status may be out of date.
The process that you detailed should work as expected in production!
+6Hi
This is a test store specific issue you’ve run into (or rather, a sandbox issue in general). The gives_access flag remains true as these test transactions are not passively refreshed as production receipts are, meaning the status may be out of date.
The process that you detailed should work as expected in production!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.