fix: align empty restore-purchases message with expected copy - #879
Merged
RUKAYAT-CODER merged 1 commit intoJul 25, 2026
Merged
Conversation
The Restore Purchases button is already wired through useInAppPurchase to mobilePayments.restorePurchases() (it restores the tier and refreshes history). Align the empty-restore message with the expected 'No purchases found to restore.' copy.
Contributor
|
Thank you for the contributing to the project. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
closes #834
Overview
Ensures the "Restore Purchases" flow behaves per the acceptance criteria.
While reviewing, the restore button is already connected: both
SubscriptionManagerandPaymentHistorycallrestorePurchases()fromuseInAppPurchase, which invokesmobilePayments.restorePurchases(), refreshes the subscription tier (so restored items unlock immediately), refreshes history, and surfaces the result in an alert.The one detail not matching the acceptance criteria was the empty-restore copy. This aligns it:
src/hooks/useInAppPurchase.ts: empty restore now returns"No purchases found to restore."(was"No previous purchases found for this account."), which both the paywall and payment-history restore buttons display.Acceptance criteria
Per the requested scope, I did not run tests or a build locally.