![]() The iOS event thats triggered when attempting to validate is. In fact if I then try to purchase the same product again Apple tells me that I have already purchased it. This is nothing to do with receipt validation. I am having some trouble with validating a Sandbox iOS receipt using Unity IAP and iOS. If I try to validate the receipt using a service such as: the validations runs smoothly, the receipt seems valid. Try removing from receipt the characters n and r and replacing + with2B before sending it to the server. you sent a sandbox receipt to the production verification server). ![]() ![]() We did not touch the IAP code for a while now, the products are always the same, this problem also does not occur for every tester: seems to impact some of them (with the same build). For that reason, always use receipt validation cautiously and as part of the overall. The environment is of course Sandbox, and everything ran smoothly for weeks, until today when we started getting those invalid receipt responses. Here are the steps needed to validate the receipt. ![]() ![]() All of a sudden we started having problems with Apple receipt validation on our Development builds. Receipt Validation plays a key role in verifying whether the auto-renewing subscription is currently active or not. Did anyone also ran into App Store problems today Apple reported an outage and it seems that the App Store delivered receipts without any signature, breaking our local receipt validation and verifyReceipt. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |