- mention the "Privacy Policy" document in the text explaining "Help us
improve Status", make a link to it and display it in a separate popup
- add a standalone header button to the settings page, doing the same
- extend storybook page with the "placement" param
Fixes#16157
* chore(links): do not open confirmation for "mailto:" links
- the domain for those is empty anyway
* chore(Settings/About): update Privacy Policy document
- change the section names and titles accordingly too
- open embedded links with an external browser
* feat(metrics): add onboarding screen metrics and section navigation
Fixes#16100
Adds metrics for navigating to the different screens of the onboarding and when navigating to a new section while logged in; only when enabled of course.
I refactored the code a little to make it simpler. I moved the check to see if the metrics collection is enabled in the async task itself, so we don't have to check it each time we add a new metric
* fix metric sent from module
* review comments
* add flowtype
This commit points to `status-jenkins-lib` version where we provide api-proxy credentials to Jenkins in CI and the desktop build would then get these env vars
- `STATUS_BUILD_PROXY_USER`
- `STATUS_BUILD_PROXY_PASSWORD`
* chore_: allow disabling http/ws api from cli
* ci: add env vars to prevent autotests hitting 8545 (#16120)
* chore: increase timeout for saved addresses test
* ci: add env vars to prevent autotests hitting 8545 port
---------
Co-authored-by: Anastasiya <82375995+anastasiyaig@users.noreply.github.com>
* wip: make the getENSName calls async
* fix: login to the app takes forever
Resolving ens name sometimes, most likely due to network congestion can be really slow,
that results in slow app loading, especially if user has more accounts, cause the app checks
ens name existence for each account.
This PR does that check in an async way.
Fixes#16086
* chore: async check for ens name existence when adding new accounts
---------
Co-authored-by: Sale Djenic <aleksandardjenic@status.im>
* chore(StatusBetaTag): make fg color configurable
* chore(StatusSwitchTab*): simplify and make the beta tag highlighted
- make the StatusBetaTag highlighted when used inside an active/checked
StatusSwitchTabButton
- simplify the components, get rid of MouseArea just for the sake of
setting the cursorShape
* fix(SendModal): hide the Custom network mode in `production`
- manage the lifetime of the Custom tab button dynamically; setting the
tab button to `visible: false` doesn't unfortunately remove it from the
tab bar
Fixes#16052
1. The DAppsListProvider needs to receive all the user accounts so that it can process all dapps the user is connected to (the dapps filtering based on selected account is an internal impl. detail)
2. Call `revokeSession` on disconnect only if the dapp cannot be found in the WC active sessions. There is some overlapping between Browser connector and Wallet connect because both operate on the same data stored in the DB. If Browser connector controller removes WC data, the WC disconnect flows cannot be successfully completed.
3. Reuse the same notification flow for Browser connector as it's used for WC
4. Fix dapp filtering when processing the dapps that will be displayed in the UI.
In this PR we get rid of `E2E_GIT_REF` parameter which would default to master or whatever value is set in CI.
We instead just rely on `env.BRANCH_NAME` to run E2E tests on the same branch the build on CI is generated from.
Co-authored-by: Siddarth Kumar <siddarthkay@gmail.com>
Added limitations:
- allowed adding of max 20 accounts
- allowed adding of max 3 watch only accounts
- allowed adding of max 5 key pairs (including the profile key pair)
- allowed adding of max 20 saved addresses per mode
Closes#15934
* feat: limits applied when running keycard flows that add new key pairs/accounts
In some rare cases hiding collectibles was causing segfault, related to
checking if all timestamps are available. Combination of 2 SFPMs with
the same source and Aggregator working on those models. Additionally
filters/sorters were depending on the Aggregator value. The minimal
crashing sample has been isolated to be investigated in a separate
ticket. In this commit aggregator's value is applied in a deferred way
via Qt.callLater, fixing the issue.
Closes: #15775