[pull] main from MetaMask:main#346
Merged
Merged
Conversation
<!-- Please submit this PR as a draft initially. Do not mark it as "Ready for review" until the template has been completely filled out, and PR status checks have passed at least once. --> ## **Description** Adds the first iteration of the mUSD conversion flow. This PR includes the core flow that we will iterate on. <!-- Write a short description of the changes included in this pull request, also include relevant motivation and context. Have in mind the following questions: 1. What is the reason for the change? 2. What is the improvement/solution? --> ## **Changelog** <!-- If this PR is not End-User-Facing and should not show up in the CHANGELOG, you can choose to either: 1. Write `CHANGELOG entry: null` 2. Label with `no-changelog` If this PR is End-User-Facing, please write a short User-Facing description in the past tense like: `CHANGELOG entry: Added a new tab for users to see their NFTs` `CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker` (This helps the Release Engineer do their job more quickly and accurately) --> CHANGELOG entry: add mUSD conversion core flow ## **Related issues** Fixes: - [MUSD-64: Mobile Proof of Concept using Transactions Confirmations](https://consensyssoftware.atlassian.net/browse/MUSD-64) - [MUSD-69: Use relay for quotes and execution in the Mobile one click proof of concept](https://consensyssoftware.atlassian.net/browse/MUSD-69) - [MUSD-42: Merge mobile mUSD conversion to production](https://consensyssoftware.atlassian.net/browse/MUSD-42) - [MUSD-86: As a user I want to see information about the relay quote when converting to mUSD so that I know how much money I will spend on fees and gas](https://consensyssoftware.atlassian.net/browse/MUSD-86) ## **Manual testing steps** ```gherkin Feature: mUSD Token Conversion Scenario: user converts stablecoin to mUSD on Ethereum mainnet (happy path) Given user has USDC, USDT, or DAI in their wallet on a supported chain When user clicks the "Convert" button next to a supported mUSD conversion stablecoin Then user sees the mUSD conversion confirmation screen And user can select from available stablecoins in the PayWith modal And user can input desired conversion amount And user sees Relay quotes with fees and estimated time And user completes the conversion flow successfully Scenario: user views unsupported token Given user has a non-convertible token in their wallet When user views their token list Then user sees the existing "Earn X.X%" CTA And user does NOT see the mUSD conversion button ``` ## **Screenshots/Recordings** <!-- If applicable, add screenshots and/or recordings to visualize the before and after of your change. --> ### **Before** <!-- [screenshots/recordings] --> ### **After** <!-- [screenshots/recordings] --> https://github.com/user-attachments/assets/be636076-79bd-4b6d-818a-6f6f5b707b06 ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots. <!-- CURSOR_SUMMARY --> --- > [!NOTE] > Adds mUSD conversion flow with Convert CTA, confirmations, global status toasts, feature flags, and localization. > > - **Earn/mUSD**: > - Add `mUSD` conversion flow with `Convert` CTA in `StakeButton` and token list for allowlisted stablecoins. > - Introduce global `EarnTransactionMonitor` and `useMusdConversionStatus` to show in-progress/success/failure toasts. > - Add `MusdConversionInfo` screen and wire into redesigned confirmations stack. > - **Confirmations**: > - Define `MUSD_CONVERSION_TRANSACTION_TYPE`; hide footer by default; add custom button label and fees tooltip; include in redesigned/full-screen types. > - Update transaction parsing/labels to recognize mUSD conversion. > - **Feature Flags/Selectors**: > - Add `MM_MUSD_CONVERSION_FLOW_ENABLED` and convertible tokens allowlist (remote/local) with symbol→address conversion. > - **Constants/Utils**: > - mUSD token constants, chain/token allowlists, and `isMusdConversionPaymentToken` helper. > - **Navigation**: > - Register redesigned confirmations route in Earn stack; mount `EarnTransactionMonitor` in main nav. > - **Localization**: > - Add strings for mUSD conversion (CTA, toasts, fees, review titles). > - **CI/Env**: > - Expose env/Bitrise flags for mUSD conversion; sample allowlist var. > - **Tests**: > - Comprehensive unit tests for hooks, selectors, utils, components (CTA rendering, navigation, error cases). > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 8a6f35d. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
…ing the omnisearch and other minor improvements (#22872) <!-- Please submit this PR as a draft initially. Do not mark it as "Ready for review" until the template has been completely filled out, and PR status checks have passed at least once. --> ## **Description** According to the [these](https://www.figma.com/design/w4EHAWR5h0OTuqeqZKaCAH/Trending?node-id=2067-19515&p=f&t=6z6WJZtGvd6H9A8L-0) designs. I have implemented the following: <img width="685" height="501" alt="image" src="https://github.com/user-attachments/assets/9e52f5b0-b16e-4b29-abab-02f0d356b1c1" /> Furthermore I have done some code cleanup 🧹 and 🐛 fixes: - Added screen sliding animation to Perps - Removed debounce from useSearchRequest - When going back from browser we should be able to go back to search results - Removed pagination dots in carrousel - Used TW in carrousel - Updated "View all >" to match styles - Updated search for trending tokens to merge Trending and non-trending tokens - Fix searchbar causing app crash due to showing and hiding element - Show loading while isDebouncing on useExploreSearch - Refactored sections to be react elements rather than functions - Adjust pills padding - Update size of section titles - Update color of search section titles - Add icons to pills - Add grey arrow in view all and change "View all" color - Change screen title to "Explore" - Change bottom menu icon and name to "Explore" - Change the icon to explore icon instead of plus [+] - Make the tab number container thinner [1] - Remove carrousel padding left to be aligned - Remove padding from section titles NOTE: There are still some bugs 🐛 that will be solved in upcoming PRs: - Clicking on native token in search throws error - Tokens from search API do not have "Volume" "Market Cap"... <!-- Write a short description of the changes included in this pull request, also include relevant motivation and context. Have in mind the following questions: 1. What is the reason for the change? 2. What is the improvement/solution? --> ## **Changelog** <!-- If this PR is not End-User-Facing and should not show up in the CHANGELOG, you can choose to either: 1. Write `CHANGELOG entry: null` 2. Label with `no-changelog` If this PR is End-User-Facing, please write a short User-Facing description in the past tense like: `CHANGELOG entry: Added a new tab for users to see their NFTs` `CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker` (This helps the Release Engineer do their job more quickly and accurately) --> CHANGELOG entry: allow navigating to a website or search on google using the omnisearch ## **Related issues** Fixes: https://consensyssoftware.atlassian.net/browse/ASSETS-1800 & https://consensyssoftware.atlassian.net/browse/ASSETS-1801 & https://consensyssoftware.atlassian.net/browse/ASSETS-1822 ## **Manual testing steps** ```gherkin Feature: my feature name Scenario: user [verb for user action] Given [describe expected initial app state] When user [verb for user action] Then [describe expected outcome] ``` ## **Screenshots/Recordings** <!-- If applicable, add screenshots and/or recordings to visualize the before and after of your change. --> ### **Before** <!-- [screenshots/recordings] --> ### **After** https://github.com/user-attachments/assets/e0994d22-01d9-4a7a-a23e-4b960b1e6675 <!-- [screenshots/recordings] --> ## **Pre-merge author checklist** - [ ] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] I've completed the PR template to the best of my ability - [ ] I’ve included tests if applicable - [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots. <!-- CURSOR_SUMMARY --> --- > [!NOTE] > Adds Explore search footer to open URLs or Google results, rebrands Trending to Explore, refactors section components/UI, and improves navigation/animations. > > - **Explore/Search**: > - Add footer actions to open direct URLs and Google searches from `ExploreSearchResults`; navigates via `TrendingBrowser` with `fromTrending`. > - Integrate token search (`useSearchRequest`) with trending results; show loading while debouncing; remove debounce delay (0ms). > - Update `ExploreSearchBar`: autofocus by type, non-destructive clear with opacity toggle, always-visible cancel, color tweaks. > - **UI Refactor**: > - Convert section config to component-based API (`RowItem`, `Skeleton`, `Section`); update usages in `SectionCard`, `SectionCarrousel`, `TrendingView`. > - Redesign QuickActions to pill buttons with icons and TW styles; adjust section headers (“View all” with arrow, sizes/colors). > - Simplify carousel (remove pagination dots; TW spacing) and align layouts/padding. > - **Navigation/Browser**: > - `BrowserTab` back behavior respects `fromTrending` to return to search; trending browser wrapper intercepts navigation. > - **Perps**: > - Enable slide-in animation for Perps stack screens. > - **Localization & Tab Bar**: > - Rename Bottom Tab “Trending” to “Explore” and change icon (`Search`); update `trending.title` and bottom nav strings. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit cab5efc. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY --> --------- Co-authored-by: sahar-fehri <sahar.fehri@consensys.net>
… cp-7.60.0 (#23128) <!-- Please submit this PR as a draft initially. Do not mark it as "Ready for review" until the template has been completely filled out, and PR status checks have passed at least once. --> ## **Description** Fixed a bug where staked energy and staked bandwidth were displaying in the swap tokens lists <!-- Write a short description of the changes included in this pull request, also include relevant motivation and context. Have in mind the following questions: 1. What is the reason for the change? 2. What is the improvement/solution? --> ## **Changelog** <!-- If this PR is not End-User-Facing and should not show up in the CHANGELOG, you can choose to either: 1. Write `CHANGELOG entry: null` 2. Label with `no-changelog` If this PR is End-User-Facing, please write a short User-Facing description in the past tense like: `CHANGELOG entry: Added a new tab for users to see their NFTs` `CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker` (This helps the Release Engineer do their job more quickly and accurately) --> CHANGELOG entry: Fixed a bug where staked energy and staked bandwidth were displaying in the swap tokens lists ## **Related issues** Fixes: #23141 ## **Manual testing steps** ```gherkin Feature: my feature name Scenario: user [verb for user action] Given [describe expected initial app state] When user [verb for user action] Then [describe expected outcome] ``` ## **Screenshots/Recordings** <!-- If applicable, add screenshots and/or recordings to visualize the before and after of your change. --> ### **Before** <!-- [screenshots/recordings] --> ### **After** <!-- [screenshots/recordings] --> ## **Pre-merge author checklist** - [ ] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [ ] I've completed the PR template to the best of my ability - [ ] I’ve included tests if applicable - [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [ ] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. ## **Pre-merge reviewer checklist** - [ ] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots. <!-- CURSOR_SUMMARY --> --- > [!NOTE] > Switches non-tradable Tron token detection to symbol-based checks using shared constants and updates tests accordingly. > > - **Bridge utils**: > - Update `isTradableToken` to determine non-tradable Tron tokens by `symbol` using `TRON_RESOURCE_SYMBOLS` (from `core/Multichain/constants`) instead of name matching. > - **Tests**: > - Adjust `isTradableToken` tests to validate symbol-based filtering (e.g., `energy`, `bandwidth`, `max-bandwidth`, mixed/upper case). > - Update `useTokens` tests to use `symbol: 'Max-Bandwidth'` and verify filtering of non-tradable Tron tokens across `tokensWithBalance`, `topTokens`, and `remainingTokens`. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 9b18269. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->
## **Description**
<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->
## **Changelog**
<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`
If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`
(This helps the Release Engineer do their job more quickly and
accurately)
-->
CHANGELOG entry:
## **Related issues**
Fixes:
## **Manual testing steps**
```gherkin
Feature: my feature name
Scenario: user [verb for user action]
Given [describe expected initial app state]
When user [verb for user action]
Then [describe expected outcome]
```
## **Screenshots/Recordings**
<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->
### **Before**
<!-- [screenshots/recordings] -->
### **After**
<!-- [screenshots/recordings] -->
## **Pre-merge author checklist**
- [ ] I’ve followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [ ] I've completed the PR template to the best of my ability
- [ ] I’ve included tests if applicable
- [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [ ] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.
## **Pre-merge reviewer checklist**
- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.
<!-- CURSOR_SUMMARY -->
---
> [!NOTE]
> Expands Sentry app state mask to include
`engine.backgroundState.AppMetadataController` (all properties) and
`user.existingUser`.
>
> - **Sentry utils (`app/util/sentry/utils.ts`)**:
> - Expand `sentryStateMask`:
> - Add `engine.backgroundState.AppMetadataController` with
`[AllProperties]: true`.
> - Add `user.existingUser: true`.
>
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
a3ac483. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
## **Description** Earn banner border and background are wrong colors ## **Changelog** CHANGELOG entry:null ## **Related issues** Fixes: https://consensyssoftware.atlassian.net/browse/MDP-398 ## **Manual testing steps** ```gherkin Feature: my feature name Scenario: user [verb for user action] Given [describe expected initial app state] When user [verb for user action] Then [describe expected outcome] ``` ## **Screenshots/Recordings** `~` ### **Before** <img width="500" alt="Simulator Screenshot - iPhone 16 Pro Max - 2025-11-06 at 12 28 10" src="https://github.com/user-attachments/assets/a1d1dab8-db90-4aff-8a14-b43ab7a69f5c" /> ### **After** <img width="500" height="2868" alt="Simulator Screenshot - iPhone 16 Pro Max - 2025-11-06 at 12 28 00" src="https://github.com/user-attachments/assets/0aaae517-ae69-45e5-9eac-0545c601a184" /> ## **Pre-merge author checklist** - [x] I’ve followed [MetaMask Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile Coding Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md). - [x] I've completed the PR template to the best of my ability - [x] I’ve included tests if applicable - [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format if applicable - [x] I’ve applied the right labels on the PR (see [labeling guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)). Not required for external contributors. ## **Pre-merge reviewer checklist** - [x] I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed). - [x] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots. <!-- CURSOR_SUMMARY --> --- > [!NOTE] > Switch Earn banner and Stake EstimatedAnnualRewardsCard to muted backgrounds without borders; update snapshots accordingly. > > - **UI**: > - `EarnInputView` banner: set background to `#3c4d9d0f`; remove `borderWidth`/`borderColor`. > - `Stake/components/EstimatedAnnualRewardsCard`: use `colors.background.muted`; remove border styling. > - **Tests**: > - Update snapshots in `EarnInputView.test.tsx.snap` to reflect new styles. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit ccc5689. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->
## **Description**
This PR refactors the Card onboarding flow to improve the KYC
verification process and user experience:
- **New VerifyingRegistration screen**: Adds a dedicated screen showing
users their registration is being verified
- **Enhanced navigation**: Restructures onboarding navigator with
`cardUserPhase` parameter, removes `Complete` screen, implements proper
navigation resets
- **Improved KYC polling**: Better polling lifecycle management with
manual `startPolling` control and automatic stopping on completion
- **Authentication UI refactor**: Updates `CardAuthentication` to use
`KeyboardAwareScrollView` and Tailwind styles
- **Code cleanup**: Replaces `useIsCardholder` hook with
`selectHasCardholderAccounts` selector
- **SDK enhancements**: Adds `getUserDetails` method and exposes
`fetchUserData` in CardSDKProvider
- **Bug fix**: Fixes `validateDateOfBirth` to accept negative timestamps
(dates before 1970)
## **Changelog**
CHANGELOG entry: Improved Card onboarding flow with new verification
screen and enhanced KYC process navigation
## **Related issues**
Fixes:
## **Manual testing steps**
```gherkin
Feature: Card Onboarding Flow
Scenario: user completes card onboarding with address verification
Given user is on the Card welcome screen
And user has not completed onboarding
When user proceeds through authentication
And user enters their physical address
And user confirms their mailing address
Then user should see the Verifying Registration screen
And KYC verification polling should start automatically
Scenario: user returns to app during verification
Given user has submitted their registration details
And KYC verification is pending
When user opens the app
Then user should be directed to the Verifying Registration screen
And polling should resume to check verification status
Scenario: user completes KYC verification
Given user is on the Verifying Registration screen
And KYC verification completes successfully
When the polling detects verification completion
Then user should be navigated to the appropriate next screen
And polling should stop automatically
```
## **Screenshots/Recordings**
<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->
### **Before**
<!-- [screenshots/recordings] -->
### **After**
<!-- [screenshots/recordings] -->
## **Pre-merge author checklist**
- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.
## **Pre-merge reviewer checklist**
- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.
<!-- CURSOR_SUMMARY -->
---
> [!NOTE]
> Refactors Card onboarding/KYC with a new Verifying Registration screen
and polling, KYC-gated home actions and alerts, SDK/user data
enhancements, updated navigation, and UI/auth improvements.
>
> - **Onboarding/KYC Flow**:
> - Add `VerifyingRegistration` screen with polling and
success/timeout/rejected states; new route
`Routes.CARD.VERIFYING_REGISTRATION`.
> - Refactor `OnboardingNavigator` to use `cardUserPhase`, fetch user on
mount, remove `Complete`, and rework initial routing.
> - Update navigation to reset stacks after phone/mailing/physical
address steps.
> - Make `ValidatingKYC` start/stop polling via
`useUserRegistrationStatus` (manual start, auto-stop on terminal
states).
> - **Card Home**:
> - Gate “Enable card” by KYC; show status/error alerts; integrate new
`useGetUserKYCStatus` hook.
> - **Authentication/UI**:
> - Refactor `CardAuthentication` to `KeyboardAwareScrollView` and
Tailwind styles; minor styles cleanup.
> - `CardWelcome` switches to `selectHasCardholderAccounts` for copies
and routing.
> - **SDK/Provider**:
> - Add `CardSDK.getUserDetails` and expose `fetchUserData` in provider;
reset onboarding on invalid ID.
> - **Hooks**:
> - New `useGetUserKYCStatus`; updates across hooks to use SDK context
shape; caching fetchOnMount=false with manual triggers in multiple
hooks.
> - **Validation**:
> - Fix `validateDateOfBirth` to accept negative timestamps (pre‑1970).
> - **Localization**:
> - Add strings for verifying registration and KYC status alerts.
> - **Routes/Selectors**:
> - Add `Routes.CARD.VERIFYING_REGISTRATION`; new selector
`selectHasCardholderAccounts`; deprecate `useIsCardholder`.
> - **Tests**:
> - Extensive updates/additions covering new screens, KYC gating,
navigator logic, hooks, SDK, and DOB validation.
>
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
73e431e. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
6 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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )