We’re going to add introuctory offers to some products in our iOS app. And we want to make sure we display the right choise for each user depending on their receipts. So it looks like we could achieve this by using
However, because it could result into refreshing user’s receipt, the AppStore sign-in dialog may appear. As I see from the current logic in the SDK it happens only when the receipt is missing in the app bundle. Which shouldn’t be the case for AppStore build. Though it’s a usual case for development and sandbox builds. Particularly the dialog appears if I try to call this method when there’s no sandbox user logged into device AppStore.
Thus we have a concern about prompting AppStore sign-in dialog unexpectedly in the process of Apple review causing a rejection. Mainly this post is the source of my concerns. And also this recommendation from Apple:
The application can advise the user that the appStoreReceipt appears to be outdated and may require refreshing
So it looks like we should precede the call to
checkTrialOrIntroductoryPriceEligibility with a user message about what is going to happen. Otherwise the AppStore sign-in will look suspiciously. Is my understanding correct?
Also it looks like this message will appear only for sandbox users (and Apple reviewers). Do you know in which cases the receipt might be missing in AppStore build?
Considering all of the above do you think it makes sense to provide a way to check for product eligibility without refreshing the receipt? That is the check could be made silently and if no receipt found locally it results in unknown status.
Best answer by codyView original