Apple verifyReceipt endpoint is deprecated

[kimesf]

The Apple endpoint to verify receipts seems to be deprecated.

See https://developer.apple.com/documentation/appstorereceipts/verifyreceipt/

I'm unsure there's interest in further supporting this verification through a different method or whether you'd be interested to add a note on README or even issuing a deprecation warning on a new release.

Just wanted to bring the issue up for now. Thanks for the gem 🙏

[gabrielgarza]

@kimesf thanks for the heads up! Correct, it's using a deprecated endpoint. At the moment everything works as expected. However we need to plan a migration onto the v2. Do you have any thoughts on this?

[kimesf]

Actually, after getting a little bit more familiar with v2, working with receipts won't be part of the new flow at all.

The whole "receipt" concept is deprecated. See https://developer.apple.com/documentation/appstorereceipts.

If there is anything to be done, it would be to follow up on apple's suggestion on the verifyReceipt page. They say that "to validate receipts on your server, follow the steps in Validating receipts on the device on your server". If you go through the recommended docs though, you'll see that the process is more complex than just calling an API and relies on information that might not be available on servers out there that use Monza.

I think migrating to v2 will often mean to abandon the "receipt" concept as a whole, while relying more on transactions and notifications to work out purchases, etc.. You can check their video update (https://developer.apple.com/videos/play/wwdc2023/10141).

My impression now is that there isn't much value in changing how Monza is validating receipts, even if it means that eventually it will be obsolete. I do think though the use of Apple features on my current project is not that extensive. Maybe other people have other use cases that might justify changes. I don't see it for my use case.