Skip to content
This repository has been archived by the owner on Apr 15, 2019. It is now read-only.

Custom node configuration is being forgotten #666

Closed
ghost opened this issue Aug 28, 2017 · 3 comments
Closed

Custom node configuration is being forgotten #666

ghost opened this issue Aug 28, 2017 · 3 comments
Labels

Comments

@ghost
Copy link

ghost commented Aug 28, 2017

Expected behaviour

If users chose custom node, it should have save it's address and pre-set last used node configuration.
If user chose for example Testnet, then after logging out and signing with new account, it should be preset to Testnet instead always to Mainnet. Same apply to restarting app itself.

Actual behaviour

It always resets itself to Mainnet and custom node configuration is forced to localhost.

@slaweet slaweet added the bug label Aug 28, 2017
@slaweet
Copy link
Contributor

slaweet commented Aug 28, 2017

I can reproduce this on latest release 1.0.2. But the current development branch no longer has this issue, since the code has been rewritten. I will keep the issue open until the next version is released.

@ghost
Copy link
Author

ghost commented Aug 28, 2017

Okay, i will confirm if it's resolved.

@ghost
Copy link
Author

ghost commented Sep 1, 2017

It's resolved on 1.1.0 rc1.

@ghost ghost closed this as completed Sep 1, 2017
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant