-
Notifications
You must be signed in to change notification settings - Fork 114
fix: [IOBP-2166] Prevent multiple wallet API calls at startup saga #7588
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
base: master
Are you sure you want to change the base?
Conversation
Jira Pull Request LinkThis Pull Request refers to Jira issues: |
PR Title Validation for conventional commit type✅ All good! PR title follows the conventional commit type. |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #7588 +/- ##
=======================================
Coverage 60.21% 60.21%
=======================================
Files 1886 1888 +2
Lines 41112 41115 +3
Branches 9539 9460 -79
=======================================
+ Hits 24754 24758 +4
+ Misses 16282 16281 -1
Partials 76 76
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
Short description
This pull request introduces a more robust mechanism for detecting external deep links and triggering wallet updates in response. The primary focus is on ensuring that when users interact with specific deep links (such as those related to wallet, payment, idpay, or cgn), the wallet state is refreshed automatically in both navigation and saga flows.
List of changes proposed in this pull request
How to test
Ensure that API calls are not triggered at startup saga and deep links are working as before
Preview
Screen.Recording.2025-11-11.at.16.32.24.mov
Screen.Recording.2025-11-11.at.16.26.05.mov
Screen.Recording.2025-11-11.at.16.27.50.mov
Screen.Recording.2025-11-11.at.16.28.58.mov