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

[Bug]: Disabling/Re-enabling Basic functionality feature causes send flow to not work #12406

Open
Unik0rnMaggie opened this issue Nov 24, 2024 · 0 comments
Labels
regression-RC-7.36.0 Regression bug that was found in release candidate (RC) for release 7.36.0 Sev2-normal An issue that may lead to users misunderstanding some limited risks they are taking team-mobile-platform Mobile Platform team type-bug Something isn't working

Comments

@Unik0rnMaggie
Copy link
Contributor

Describe the bug

When disabling the Basic functionality feature from Security & Privacy the Send feature does not work:

  • On Ethereum Mainnet the Next button is greyed on
  • On other networks, the insufficient funds message is shown

Also when disabling the Basic functionality feature:

  • The token graphs are not loaded
  • The token balance for all tokens except native tokens is greyed out, showing a black line instead (for networks: Ethereum Mainnet, Arbitrum, Linea)

When re-enabling the Basic functionality feature, the token graphs are showing, but send flow still does not work and token balance is still not displayed.

Expected behavior

Be able to send

Screenshots/Recordings

Basic.functionality.Ethereum.Mainnet.mov
Basic.functionality.BNB.mov

Steps to reproduce

  1. Go to Settings and Security & Privacy
  2. Disable Basic functionality feature
  3. Click on any token and notice the graphs are not loading
  4. Notice token balance is not showing for non-native tokens, but a black line is showing instead
  5. Click on Send
  6. Notice unable to send on any network
  7. Re-enable the Basic functionality feature
  8. Notice the token graphs are loading, but balance is not.
  9. Click on send
  10. Notice unable to send

Error messages or log output

No response

Detection stage

During release testing

Version

7.36.0

Build type

Other (please specify exactly where you obtained this build in "Additional Context" section)

Device

Google Pixel 6 Pro

Operating system

Android

Additional context

I obtained the build from here

Severity

No response

@Unik0rnMaggie Unik0rnMaggie added the type-bug Something isn't working label Nov 24, 2024
@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by team Nov 24, 2024
@github-project-automation github-project-automation bot moved this to To be fixed in Bugs by severity Nov 24, 2024
@Unik0rnMaggie Unik0rnMaggie added the regression-RC-7.36.0 Regression bug that was found in release candidate (RC) for release 7.36.0 label Nov 24, 2024
@jvbriones jvbriones changed the title [Bug]: Disabling Basic functionality feature causes send flow to not work [Bug]: Disabling/Re-enabling Basic functionality feature causes send flow to not work Nov 25, 2024
@Unik0rnMaggie Unik0rnMaggie added team-mobile-platform Mobile Platform team Sev2-normal An issue that may lead to users misunderstanding some limited risks they are taking labels Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
regression-RC-7.36.0 Regression bug that was found in release candidate (RC) for release 7.36.0 Sev2-normal An issue that may lead to users misunderstanding some limited risks they are taking team-mobile-platform Mobile Platform team type-bug Something isn't working
Projects
Status: To be fixed
Status: To be fixed
Development

No branches or pull requests

1 participant