fix(suite-native): after coin enabling is enabled, show relevant normal accounts #14228
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
matejkriz
reviewed
Sep 10, 2024
matejkriz
reviewed
Sep 10, 2024
matejkriz
approved these changes
Sep 10, 2024
|
For a reference, the migration is not used because it has to happen when device is connected, not on app start. |
|
/rebase |
|
Start rebasing: https://github.com/trezor/trezor-suite/actions/runs/10795107265 |
trezor-ci
force-pushed
the
fix/native/coin-enabling-update
branch
from
5e9aa79
to
b447d65
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When checking for discovery updates, make sure that first normal account is visible for enabled networks when coin enabling is active.
This might be needed in case user has View only device from before coin enabling was active in such case the first normal account can be invisible. We need to make it visible.
Related Issue
Resolve #14225