You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I randomly generated passphrase on android wallet and wrote it down 'on paper' (No copy & paste function) , with the format and order provided . Account created and logged in successfully.
Later on, I get back to PC - Qbundle. I put in the same passphrase , login succeed, but the account address/ID is different, I found out that its a new account (new hash index i supposed).
Finally, i found out that I didn't key in 'spaces' between passphrase words, and there aren't any hints/settings to remind 'spaces' between words inside QBundle or android wallet. I guess some users would lose the account forever if they don't figure out 'spaces' issue, unless they choose 'create own passphrase' and set any phrase without spaces.
Please check that out and hope better ui/ux, i suppose most users like me are lazy and sometimes lose focus on details.
Cheers.
The text was updated successfully, but these errors were encountered:
I randomly generated passphrase on android wallet and wrote it down 'on paper' (No copy & paste function) , with the format and order provided . Account created and logged in successfully.
Later on, I get back to PC - Qbundle. I put in the same passphrase , login succeed, but the account address/ID is different, I found out that its a new account (new hash index i supposed).
Finally, i found out that I didn't key in 'spaces' between passphrase words, and there aren't any hints/settings to remind 'spaces' between words inside QBundle or android wallet. I guess some users would lose the account forever if they don't figure out 'spaces' issue, unless they choose 'create own passphrase' and set any phrase without spaces.
Please check that out and hope better ui/ux, i suppose most users like me are lazy and sometimes lose focus on details.
Cheers.
The text was updated successfully, but these errors were encountered: