-
Notifications
You must be signed in to change notification settings - Fork 430
Release builds used via TestFlight will verify receipts against the wrong server #255
Comments
Hello @warpling Do you have the code to fix it? Regards |
Yes! Again the steps to handling the Sandbox are as follows:
Tweaks to makeI first added the private ivar
Then in
Then I updated
|
it works perfect! Thank you! |
😊 I hope this can help others. I'd make a PR but it seems like the project isn't getting any merge love these days. ~Ryan On Jan 20, 2016, 9:53 AM -0800, josueruiz7notifications@github.com, wrote:
|
@warpling I have an issue, maybe you can help me, I am trying to validate: if([[MKStoreKit sharedKit] isProductPurchased:ID]) { } But it seems that store cache, because when I first log in with an appleid that already has buy the product , it works perfect, but when I log out and log in with other appleId that has not bought the product, THIS VALIDATION still return true. Did you get this issue? :( Thanks. |
Yikes, I've run into lots of weird issues with the Sandbox I'm afraid. Have you tried reinstalling the app? |
Yes , it works reinstalling the app, I figure out that the issues is on "appStoreReceiptURL", it seems to be cached or some thing like that. :S NSURL *receiptURL = [[NSBundle mainBundle] appStoreReceiptURL]; |
I've always had to delete the app to reset purchases. Even then, sometimes when I reinstall they quickly get restored if I forget to log out of the sandbox account. |
Hi @warpling I changed of library, I used the follow: https://github.com/robotmedia/RMStore |
Ah neat! I'll look into using that. |
Release builds will attempt to verify receipts against the production verification server, but release builds distributed via TestFlight should validate against the Sandbox server. Verifying sandbox receipts against the production server results in the error:
Apparently Apple's recommended method of handling this is to first attempt to validate against the production server and if that fails with error code 21007, try the request again with the Sandbox server. This should definitely make it into a future release! :)
The text was updated successfully, but these errors were encountered: