Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Empty array on in_app receipt field / Implement SKReceiptRefreshRequest #111

Closed
brunolemos opened this issue Jul 26, 2017 · 3 comments
Closed

Comments

@brunolemos
Copy link

brunolemos commented Jul 26, 2017

Some users are complaining they are paying and not receiving the subscription.

Debugging the server, I noticed it receives the same receipt-data from the user on every receiptData request, with an empty array on in_app field.

After searching some links (e.g. this one), I believe we need to call Apple's SKReceiptRefreshRequest method to get an updated receipt from Apple's server.

Is that correct to assume? Or maybe another thing is causing this issue?

Apple docs:

An empty in_app array indicates that StoreKit has not recorded any transactions for that user yet. It may be that the application receipt has not yet been updated. When this happens, your app can inform the user that the receipt does not appear current and ask whether to refresh it. Upon user agreement, your app should use the SKReceiptRefreshRequest class to update the receipt. At this point, if StoreKit has recorded a purchase for the user, your app receipt will show it in in_app. See Refreshing the App Receipt for more information on how to update a receipt.

@chirag04
Copy link
Owner

there is a PR in works for refreshReceipt. let's continue there: #110

@lazyhoneyant
Copy link

@brunolemos Do you solve this problem by refresh? I have the same issue too. the receipt has no in_app fields,(empty array []). but refresh didn't solve it.

@brunolemos
Copy link
Author

@lazyhoneyan no, I haven't looked at this probably anymore, not sure if I still have it, users stopped complaining

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants