This repository was archived by the owner on Mar 15, 2018. It is now read-only.
New API for receipt checks on start (bug 981235) - #15
Merged
Conversation
Contributor
Author
|
Got some great feedback from @mstriemer. The purchase callback is now inline which makes code easier to read. The init callbacks are still in flux; those are coming next. |
kumar303
added a commit
that referenced
this pull request
Jun 12, 2014
New API for receipt checks on start (bug 981235)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Any r on the new API? You could ignore all the diff churn and just check the readme.
This change sets the stage for receipt verification which needs to happen when an app first loads. The purchase function will now invoke the same
onpurchase()callback as receipt restoration would. However, receipt restoration will land in a future bug.