Skip to content
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

Restore is always considered successful if no error occurs #4222

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

jamesrb1
Copy link
Contributor

@jamesrb1 jamesrb1 commented Aug 26, 2024

If a user restores purchases, but no purchases are available to be restored, the completed callback does not get called. This fixes the issue.

@jamesrb1 jamesrb1 added the pr:fix A bug fix label Aug 26, 2024
@vegaro
Copy link
Contributor

vegaro commented Aug 27, 2024

I’ve also found confusing in the past the fact that the callback is not notified if nothing is restored, so I am happy that is changing. FWIW, this PR is the one that changed it intentionally #3233 and I think the original idea, of not not displaying “Purchases restored successfully” is good, but the side effect of not notifying the callback is more confusing in my opinion than displaying the dialog.

I agree with your points of looking for a better solution for this, which would be displaying a dialog that says "Nothing was restored" and calling the callback feels like the proper solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr:fix A bug fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants