![]() ![]() with jailbroken devices) is less secure than receipt validation done through a server you control. In all cases the two worlds, sandbox and production, are always separated.ĭon't forget also that with iOS7 added a new safer way to manage receipt validation directly from the device: consider in fact that receipt validation directly from the client (that you don't fully control, e.g. This should cover your development needs and of course fake receipts will fail validation too.īy the way, and this is officially stated in the documentation ONLY for subscriptions, if you try to validate a sandbox receipt with the production server you will get a specific status code there is another status code that covers the case of production receipt validated with the sandbox server. if previous validation failed, just validate the receipt with the sandbox server.If the receipt is validated, you're done. always validate the receipt with the production server first, this will apply for 99% of your app life. ![]() Then you send the app to review, you clearly hard coded your app to validate the receipt with the production server.īut nothing prevents you from doing the validation in two steps: What happens is that when you develop you hard code your app to validate the receipt with the sandbox. The session was related to subscriptions but you can extend it for in app purchases. The solution is quite simple and it was explained on session 308 of WWDC 2012 (the video is available for registered developers). Viewing 11 posts - 1 through 11 (of 11 total) Author Posts Jat 18:35 21838 Ginzo Milani I have setup literally everything properly, I need my binary to be accepted so my In-App purchases go live which Alex suggested is the reason my In-App purchases are failing.
0 Comments
Leave a Reply. |