BDK-How to handle expired re-subscribers In-app purchases

Hi everyone, I was hoping someone here have experience handling in-app purchases with BDK and how to solve the use case of expired subscribers coming back and re-subscribing. Right now, my workflow is the following,

  1. Have the user click a button to verify that they don’t have an active subscription
  2. if they don’t, they get redirected to re-subscribe a new one.

The problem is when they click to purchase a new subscription, the old data from their expired subscription (old expiry date and app receipt) keeps getting captured and destroys the whole flow.

Has anyone experienced this? Any insight or tips would be much appreciated!

Still struggling with this anyone have any tips?

This topic was automatically closed after 69 days. New replies are no longer allowed.