Skip to content

[Bug]: Settings - Whenever disabling Basic Functionality some settings are disabled but some are kept enabled (despite being disabled) #40081

@seaona

Description

@seaona

Describe the bug

There's a miss-alignemnt on how settings behave (are changed) whenever Basic Functionality is disabled.
Some settings are disabled, but some other keep the toggle enabled despite being disabled in reality (ie Security Alerts, DEcode Smart Contracts, Estimate balance changes).

Extra note: whenever Basic functionality is enabled, all toggles are re-enabled except Metametrics -> that is expected for Legal reasons.

Expected behavior

We should align the behaviour of the toggles --> all 3rd party toggles should be automatically disabled if Basic Func is disabled?

Screenshots/Recordings

settings-basic-func-misalignment.mov

Steps to reproduce

  1. Go to Security Settings
  2. Disable Basic Functionality
  3. See some toggles which use 3rd party requests, remain enabled (despite being disabled in reality)

Error messages or log output

Where was this bug found?

Live version (from official store)

Version

13.16.0

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

No response

Severity

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-triageIssue needs to be triagedregression-prod-13.16.0Regression bug that was found in production in release 13.16.0team-core-extension-uxCore Extension UX teamtype-bugSomething isn't working

    Type

    Projects

    Status

    To be triaged

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions