This repository was archived by the owner on Mar 4, 2020. It is now read-only.
Bug fix issue #221, changed kMKStoreKitProductPurchasedNotification object #235
Conversation
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
Pass the transaction object instead of the productIdentifier in the notification
Created the pod spec file
Changed the pod spec extension to .json
This may fix the issue MKSG-MugunthKumar#221
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I added a check on line 331 on the originalAppVersion string and saved the purchaseRecord only if this string is not nil. Plus I did a modification on the
kMKStoreKitProductPurchasedNotification: instead of postingtransaction.payment.productIdentifierI post the entire transaction object so I can take the transaction identifier back and use it for a server side validation