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

Stored addresses should be correctly handled according to network #3200

Closed
Bitcoinera opened this issue Nov 25, 2019 · 3 comments
Closed

Stored addresses should be correctly handled according to network #3200

Bitcoinera opened this issue Nov 25, 2019 · 3 comments
Assignees
Labels

Comments

@Bitcoinera
Copy link
Contributor

Bitcoinera commented Nov 25, 2019

Is your feature request related to a problem? Please describe.

If I am in a network and now connect to another one and try to log in, I get as possible addresses the ones from the last network I logged in, but not the ones from the other networks.

So, for example, if I am signed in in Regen, and now want to switch to Cosmos, and go to the Sign In, I get as recommended addresses in the "Explore with any address" the ones from Regen, and it doesn't remember the ones from Cosmos.

image

This is really poor UX.

Describe the solution you'd like

As an user, I want Lunie to always remember my different addresses for each network. And only remind me of my addresses in the network I now want to sign in.

Describe alternatives you've considered

Additional context

@Bitcoinera Bitcoinera self-assigned this Nov 25, 2019
@Bitcoinera
Copy link
Contributor Author

And now after logging in into Cosmos and try to switch back to Regen I see both addresses from the two networks as recommended:

image

This can lead to pretty awful errors! 😨

@stale
Copy link

stale bot commented Jan 13, 2020

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale label Jan 13, 2020
@Bitcoinera
Copy link
Contributor Author

Oops, I will close this one since I already opened the following feature request which handles this: #3389

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant