-
-
Notifications
You must be signed in to change notification settings - Fork 647
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
Finish transaction is called too quickly #581
Comments
I'll go ahead and try to solve this on the iOS side but I'd be very happy if someone could tell me if this is handled on the Android side? |
This seems to serve the same purpose as acknowledging a purchase on Android so it should fit well into that existing api. Edit: that should be consumeAsync for consumables. |
Could you kindly support us with |
Absolutely, I'll try to make time to do a PR next week. In the meantime here is the apple documentation that explains that one should deliver the purchased material before calling finishTransaction and that SK will persist and keep providing the transaction to the observer until finish has been called. The Provide Content and Finish the Transaction section in this document |
I believe the correct way to handle this would be to simply expose the finishTransaction method in the react-native-iap library. To avoid breaking changes I'd suggest adding a parameter |
@solidfox Sounds great!! Looking forward for your |
@solidfox How are you going with this? Would you prefer better performance if we can reward on the update? I will charge extra $30 for this for your help. |
@hyochan has funded $30.00 to this issue.
|
@hyochan I started working on it today but got a bit caught up in getting the example running only to realize that the example isn't able to make purchases anyway so I guess I'll test it in my own use case. I also noticed the remains of this commit that seems to be trying to achieve what I'm doing: edfbd12 Only seems to be cruft left though so I guess it was removed at some point? |
Would it be possible to get access to the flow in the documentation to add in registering the purchase with the apps server and acknowledging / finishing the transaction? |
@hyochan Thanks! You can send the invite to daniel.schlaug at gmail. |
@solidfox I've just shared the diagram to your |
@hyochan has rewarded $21.00 to @solidfox. See it on IssueHunt
|
* 'master' of https://github.com/dooboolab/react-native-iap: (107 commits) Release 3.3.4 Keep valid SKUs in memory chore(package): update flow-bin to version 0.103.0 Fixes hyochan#600 Added missing types on updates in 3.3.0 chore(package): update @types/react-native to version 0.60.2 Release 3.3.1 (hyochan#596) Update travis with yarn Fix flow type for purchaseUpdatedListener Upgrade example project rn version chore(package): update @types/react-native to version 0.60.1 Fix hyochan#581 finishTransaction called automatically (hyochan#589) Update index.js.flow chore(package): update lockfile yarn.lock chore(package): update @types/react-native to version 0.60.0 chore(package): update lockfile yarn.lock chore(package): update @types/react to version 16.8.23 Fixes hyochan#577 (hyochan#578) Update @types/react-native to the latest version 🚀 (hyochan#575) Improve README (hyochan#574) ... # Conflicts: # ios/RNIapIos.m
Version of react-native-iap
3.2.4
Version of react-native
0.59.9
Platforms you faced the error (IOS or Android or both?)
iOS (Android not yet confirmed)
Expected behavior
Actual behavior
Tested environment (Emulator? Real Device?)
This can be determined directly from this line of code: https://github.com/dooboolab/react-native-iap/blob/df1483db059cddeb6fd1244d583288e5e7f6b20e/ios/RNIapIos.m#L414
Steps to reproduce the behavior
IssueHunt Summary
solidfox has been rewarded.
Backers (Total: $30.00)
Submitted pull Requests
Tips
IssueHunt has been backed by the following sponsors. Become a sponsor
The text was updated successfully, but these errors were encountered: