-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Adds receipt validation endpoint #515
Adds receipt validation endpoint #515
Conversation
@flovilmart updated the pull request. |
It also add a Any other Schema could benefit that feature as it's baked into the |
Looks great, minus style nits, but they don't matter here, since we don't have jslint/jshint/etc yet... (it's coming). I can help test this e2e with App Store next week, if you need it... |
your call! |
Ok, great... Do we want to wait for e2e test or merge as is and then test? |
Adds receipt validation endpoint
W00t! |
🎉 🍻 |
So, sorry for the question, but does parse server now fully support the SDK's class PFPurchase and all its methods, including restore? |
I seem to be able to do purchases through PFPurchase, but restore seems to break with the following error: Error Domain=NSCocoaErrorDomain Code=3840 "JSON text did not start with array or object and option to allow fragments not set." UserInfo={NSDebugDescription=JSON text did not start with array or object and option to allow fragments not set.} Thanks for a great piece of software! |
Can you provide the logs when running with VERBOSE=1? Not sure we implemented the restauration end points. |
Not having a restore purchases button is grounds for app rejection on the Apple App Store :( Here's the heroku-side output with VERBOSE=1: 2017-02-09T05:27:36.568640+00:00 app[web.1]: verbose: REQUEST for [POST] /parse/validate_purchase: { |
Proposed fix for #134
Exposes
/validate_purchase
endpoint like expected in the iOS SDK.