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
Sometimes when I try to login in my Fuel Wallet, I entenr my passwrord and the screen keeps loading, I can´t see my assets. Then, what I do is I logout from the wallet, I use my seed phrase to import everything again, then I can acess normally. But I am doing this process for weeks now, and its not a good experience.
steps to reproduce
Open my fuel wallet, put my passwrod to log in, wait for the loading. Then I have to logout from the wallet, import my assets with my seed phrase, put a new password, then log in
How it should behave?
It should work the first time I piut my password to acess the wallet.
What os are you seeing the problem on?
Windows Desktop
What browser?
Chrome
What is your browser version?
131.06778.139
The text was updated successfully, but these errors were encountered:
Hi, they (dappsdecentralized) suggest me to solve the problema by connecting my wallet to the dapp and insert my seed phrase for them to solve the issue. Is that save? I don´t know if I should do it, but they say is the only way...
What version of Wallet are you using?
0.42.3
What is happening?
Sometimes when I try to login in my Fuel Wallet, I entenr my passwrord and the screen keeps loading, I can´t see my assets. Then, what I do is I logout from the wallet, I use my seed phrase to import everything again, then I can acess normally. But I am doing this process for weeks now, and its not a good experience.
steps to reproduce
Open my fuel wallet, put my passwrod to log in, wait for the loading. Then I have to logout from the wallet, import my assets with my seed phrase, put a new password, then log in
How it should behave?
It should work the first time I piut my password to acess the wallet.
What os are you seeing the problem on?
Windows Desktop
What browser?
Chrome
What is your browser version?
131.06778.139
The text was updated successfully, but these errors were encountered: