Android subscriptions upgrade, downgrade and change #350
Conversation
This file contains 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
|
@jamesmontemagno Hello, is there a chance to merge this pull request (or any other Android subscription update implementation)? If so, when? |
|
@jamesmontemagno Hello, any update here? :) |
This was referenced Feb 27, 2021
|
|
If this can be rebased on the latest and updated to the latest android billing which is now used I will pull it in. |
|
I will check everything with latest version asap. |
|
@jamesmontemagno I've created new pull request ( #404 ), this time compatible with Google Play Billing Library 4.0.0. Checked this new implementation in my own app and it seems to works perfectly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #26
Changes Proposed in this pull request:
New UpgradePurchasedSubscriptionAsync function is implemented for Android. It uses similar interface as #192 but implementation works fine with latest api. Implementation for iOS is not necessary, because iOS support upgrades/downgrades itself. I didn't check UWP.