-
Notifications
You must be signed in to change notification settings - Fork 37
Validate in-app purchase receipts? #17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Yes, that would be nice! I'll gladly accept pull requests. |
I created a patch for it :)
I think I did the biggest part of the job, now it's just a matter of deciding how users should pass info to validate extracted data. |
I added a new commit, fixing some issues. Please take a look at the commit log:
I think the patch is now much better, and much more stable. |
Many many thanks for all the patches! Please give me a couple of days to look at them, I'm kind of busy and Christmas is coming fast. But I will look at this, promise! |
Thank you. |
Any news on this? |
(still waiting :) ) |
@ItalyPaleAle Whats the status on this? Was all your code already merged? I found a bug that prevents all the in app purchase receipts from being loaded. The code will only load 1 in app purchase receipt right now. I can provide a fix if all your code has been included already. |
@flexxxx Sorry, I haven't used this in over 7 years at this point :( |
On Lion, in-app purchase receipts are stored inside the MASReceipt/receipt file, in a separate section.
Is it possible to include support for them in this (excellent) library?
Thank you!
The text was updated successfully, but these errors were encountered: