MetaMask / MetaMask/metamask-mobile
Fix Misleading Money Account Deeplink Handling
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 1.7k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 669
Description
## Issue
Money Account Marketing went out yesterday at 10 EST. A new section on [metamask.io/money](https://metamask.io/en-GB/money) shows "Get started" as the main deeplink entry point. The deeplink leads to a **resource not found** page in 3 scenarios:
- While the app is rolling out — and not yet available to that user
- Geo blocked
- Money is in a disabled state (due to a feature flag or something else)
### Caused by
The current Money account deeplink handler leading to an old error page.
## Acceptance Criteria
Fix the `handleMoney` deeplink handler to support the following states:
- **Money account is enabled (happy path)**
- Redirects to Money onboarding if user hasn't seen it and it's enabled; otherwise, redirects to Money Home
- **Money account is disabled (e.g. maintenance)**
- Displays the "Money account unavailable" bottom sheet
- **Money account is enabled but user isn't part of gradual rollout cohort**
- Displays the "Money account coming soon" bottom sheet
## References
- Jira: [MUSD-1096](https://consensyssoftware.atlassian.net/browse/MUSD-1096)
- PR to main: https://github.com/MetaMask/metamask-mobile/pull/32622
[MUSD-1096]: https://consensyssoftware.atlassian.net/browse/MUSD-1096?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
Contributor guide
Research direction
Start at the handleMoney deeplink handler and trace its existing routing and bottom-sheet behavior for the three states described in the acceptance criteria. Verify that enabled users reach onboarding or Money Home, disabled users see the unavailable sheet, and users outside the rollout cohort see the coming-soon sheet; the issue references PR #32622 as work already in progress.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100