Improved Callback and Error Handling#86
Conversation
Bump to version 2.4.2
package.json
Outdated
| { | ||
| "name": "react-native-billing", | ||
| "version": "2.4.0", | ||
| "version": "2.4.2", |
There was a problem hiding this comment.
I'll review this PR in more detail later. But please do not manually update the version number in PR.
There was a problem hiding this comment.
Why is this? As part of these changes we expect the version to be incremented. It doesn't make sense for us to downgrade this as we increment it for proper cache/references in lockfiles.
There was a problem hiding this comment.
What you do for forks is not up to me. But for upstream, i.e. this repository, I want to increment the version myself. This is because I might add other changes along with this version.
There was a problem hiding this comment.
Makes sense! Thanks @cbrevik -- we will update this.
|
Ok, reverted to 2.4.0, you can do a squash now. We are ok with this being merged =) @cbrevik |
|
Cool, I'll look into this tomorrow! Has the code been tested by you in your app(s)? |
|
Yep we have used it in our apps and through that testing is how we resolved the various callback issues. |
|
It will be great to see this pull request to be merged soon! 😃 |
|
I'd tried this pull request, but I'm still getting no callbacks from some functions like InAppBilling.getProductDetailsArray. It appears this fix doesn't solve the problem. |
|
After this PR 'purchase' doesn't return transactionDetails. It returns 'true'. |
|
@freiserg I have the same issue. This PR breaks the current functionality of the lib and should be marked as a breaking change with the associated readme updates. A current workaround is: Purchase -> loadOwnedPurchases -> listOwnedSubscriptions / products -> validate each receipt |
|
I'll look into this. Resolving with |
|
I've reverted this PR, and added a new function. I'd recommend re-testing with the newest version of this lib ( |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
@idehub here are the edits we made for improved and proper handling with in-app-billing-v3
Related and resolves #85