we have a question about our in-app purchase flow. We pushed a new update to review. We changed the in-app purchase flow where we actually just changed the order when the receipt validation is done.
Cause we don’t know if the user has a valid subscription we have to fetch the receipt first which leads to the password prompt (which is the normal behaviour as we understand correctly in not production environment). Then comes the validation and depending on the result we show the auto-renewing subscription page or we pass the requested action.
So our flow is:
1. Fetching receipt
2. Validating receipt
3. If
valid - Pass requested action
not valid - show auto-renewing subscription page where the user can make the in-app purchase
Now apple comment in their rejection that they don't see the auto-renewing subscription page instead they got the password prompt from Itunes Store.
As we understand correctly the password prompt is the normal behaviour in a not production environment but apple seems to dont expect this behaviour. We changed nothing in the way how we fetch the receipt.
Is our flow incorrect or how can we validate if the user has a valid subscription without fetching the receipt? We're a bit confused here. Can someone can give us any advice here?