-
Notifications
You must be signed in to change notification settings - Fork 225
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
[IOS] Transaction receipt became encoded #297
Comments
Example of transactionReceipt I received: |
Apple returns encoded Receipt data. We have to use this encoded string for receipt validation? |
Hi @hamza39460, as I see you use subscriptions in your product. Could you please test my pull request and probably add your functionality? |
@hamza39460 Thanks for your interest! I hope you to be the tester of #301 firstly. You can check how to get a package from git branch here. |
Hi thanks for offering me to test #301 first. But I can only test it for IOS In App Purchase (Subscription based), if its okay for you I will surely do it. |
@hamza39460 thanks, any progress will be super help |
@bohdan1krokhmaliuk Hi I have tested the iOS subscriptions it. all working good. |
Thank you :) |
This issue is stale because it has been open 90 days with no activity. Leave a comment or this will be closed in 7 days. |
Version of flutter_inapp_purchase: 5.0.1
Platforms you faced the error: IOS
Expected behavior:
PurchasedItem.transactionReceipt contains JSON string, which was previous behavior.
Actual behavior:
Noticed today that all of my purchases fail to validate (on test environment) as now PurchasedItem.transactionReceipt contains base64 encoded string. Also orderId, purchaseToken originalTransactionIdentifierIOS and originalTransactionDateIOS are null (in PurchasedItem object)
Tested environment:
Real devise, test environment. Probably after accepting the latest agreements
Steps to reproduce the behavior
Whenever you fetch PurchasedItem with transactionReceipt for IOS - it will be base64 encoded string
The text was updated successfully, but these errors were encountered: