-
Notifications
You must be signed in to change notification settings - Fork 53
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
[CSDK-302] Fix: attempt to reconnect when billing response is error #558
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes a lot of sense to me 👍🏻
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense to me too!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a question, but I think it shouldn't matter in this case
BillingClient.BillingResponseCode.SERVICE_UNAVAILABLE, | ||
BillingClient.BillingResponseCode.USER_CANCELED, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm should we retry on a USER_CANCELED
response code? Though I guess we shouldn't get this code in the onBillingSetupFinished
callback and this is just to complete the cases, seems like it could be part of the codes where we don't retry? Just would like to understand why it was put here.
Checking our code against Google's example, it strikes me that there are a couple of instances where we're not actively retrying the connection, but Google is (and it seems reasonable).
So I added those cases.
https://revenuecats.atlassian.net/browse/CSDK-302
Another attempt at solving #553