Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>In what I've seen, iOS7 doesn't change the need for whether or not you <strong>should</strong> do receipt validation, just <strong>how</strong> receipt validation is possible. iOS7 has enabled receipt validation on the device (e.g., see link from <a href="https://stackoverflow.com/users/1226963/rmaddy">https://stackoverflow.com/users/1226963/rmaddy</a> above, and see <a href="https://stackoverflow.com/questions/19943183/a-complete-solution-to-locally-validate-an-in-app-receipts-and-bundle-receipts-o">A complete solution to LOCALLY validate an in-app receipts and bundle receipts on iOS 7</a>). </p> <p>Does on-device receipt validation add extra security? It seems to me that it does. It gives you one more tool with which to secure your purchases. In my app (yet to be released), I want to support iOS6 and iOS7 so I decided to have a back-end server to do receipt validation for the iOS6 case. And since I have that server in place, for iOS7 receipts, I do on-device validation first and if that succeeds, I do server validation as a second check.</p> <p>Whether or not you do receipt validation (in iOS5, iOS6, iOS7 etc) really depends on how much your security means to you. If you don't have much in the way of security needs, then why spend much time on security. If you do, then do more.</p> <p>What if Apple changes the format of the receipts? Well, of course, this can and likely will happen. Given that the iOS6 to iOS7 change restructured receipts and in-app purchases considerably, it seems we should expect iOS8 to do so again. That's the future. Deal with what we have now.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload