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

"From" page is not skipped after long tapping "Send" on the wallet main page #20479

Closed
VolodLytvynenko opened this issue Jun 17, 2024 · 0 comments · Fixed by #20773
Closed

"From" page is not skipped after long tapping "Send" on the wallet main page #20479

VolodLytvynenko opened this issue Jun 17, 2024 · 0 comments · Fixed by #20773
Assignees
Labels
feature feature requests medium-prio test cases required wallet-core Issues for mobile wallet team

Comments

@VolodLytvynenko
Copy link
Contributor

VolodLytvynenko commented Jun 17, 2024

It might be good to fix this together with #20472

Steps:

  1. Go to the wallet main page
  2. Long tap the asset -> tap 'send' option

Actual result:

The FROM page is shown

collectibleslist.mp4

Expected result:

  • If "Send" button is long-tapped from Wallet Home page and the selected token or collectible to be sent is available on at least two accounts
    • If the user has Account 1 (with 1 DAI), Account 2 (with 0 DAI), then the FROM page should be skipped.
    • If the user has Account 1 (with 1 DAI), Account 2 (with 1 DAI), and Account 3 (with 0 DAI), then on the FROM page, the user should see only Account 1 and Account 2. Account 3 should not be present or should be disabled.

discussed with the design team: https://discord.com/channels/624634427930312714/1248618318735081544/1252261800716668989

OS:

IOS, Android

Devices:

  • Pixel 7a, Android 13
  • iPhone 11 Pro Max, IOS 17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature feature requests medium-prio test cases required wallet-core Issues for mobile wallet team
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants