Hi there,
I did find a similar post to what I wanted to ask here, but it’s now closed for comments:
Our context is that we implemented and shipped IAPs ourselves, before we decided RevenueCat was worth trying out. We didn’t store the raw base64 receipts, because Apple actually discourages and deprecated the /verifyReceipt endpoint last year. We did store every transaction ID, though, and —as that post notes — we’re able to get the full transaction info securely and verifiably through the App Store Server API.
Since we don’t have the base64 receipts, we indeed went with a client-side migration path, but the result is that RC’s data even a week+ after shipping is incomplete. We’re trying RevenueCat out now, but it’s been really hard to trust and rely on RC data when we can see the numbers are still incomplete and inaccurate (like still 30% off in some cases!!).
Is there any way you all could reconsider this limitation? This would be very meaningful to us.
Could you also share more about what additional info you get from the receipts that you don’t from the App Store Server API these days?
Even if there is such additional info, is there any way you could still support importing historical transactions *without* that additional info?
Thank you for the consideration!
