Failure to create a new wallet when a previous wallet created and password is forgotten about jam HOT 8 OPEN

As a user I found it confusing, I think there should be an active and then an unlocked.

from jam.

What about adding this to an FAQ section to the readme. I'd be happy to submit that as a pr.

Hey @Devinml, really appreciate your thinking and willingness to help. Thanks brother.
Since this is the first time someone asked, it is not really a "Frequently Asked Question".

Okay for you to wait and see whether other people have a similar issue with this? Thanks again 🙏

from jam.

Hey @Devinml!

Thanks for the report. 🙏

Yes, indeed, that is a problem. However, the password is needed in order to "lock" an active wallet and "unlock" or create/import another one. A possible workaround is to restart the service (e.g. with a system reboot). I do not think there is anything that can be done otherwise (but I might be wrong!).

from jam.

but lets add this piece of information also:

"… if you have forgot your password, restart the service so that this wallet gets locked and you can proceed."

(bad wording I know)

from jam.

but lets add this piece of information also:

"… if you have forgot your password, restart the service so that this wallet gets locked and you can proceed."

(bad wording I know)

Aww man.. Do you really think that is necessary?
Let's wait at least for an additional report of such a situation before we clutter the UI for such niche situations. Or am I on the wrong track here?

from jam.

What I would do is renaming the active label from "Unlocked" back to what we had earlier: "Active".
(It is strange to unlock something that is already unlocked, is it not?)

from jam.

As a user I found it confusing, I think there should be an active and then an unlocked.

Yeah, but that would not really resolve the problem at hand. You need a valid session token to lock or unlock the active wallet in order to create/import a new one. There is only so much you can do, if a user forgets the password. I am afraid, there is nothing we can do about it technically, but at least try to reduce the confusion.

from jam.

What about adding this to an FAQ section to the readme. I'd be happy to submit that as a pr.

from jam.