Did you search for similar issues before submitting this one?
Yes
Describe the issue you encountered:
While trying to recover a wallet, my network connection went down. The error message from the system indicated that my keys were somehow incorrect. Once the network connection was restored, the keys worked without issue.
Expected behavior:
The system should display appropriate error messages.

Groundwork laid by @mrose17 w/ https://github.com/brave/browser-laptop/pull/5924
This is ready for the UI work. Marking as 0.13.1 and assigning over to @jkup
@bsclifton did you mean to close this?
it shouldn't have been closed. i did the first part, but now it's up to you!!!
Looks like the self-closing keywords from the commit unintentionally closed it :smile:
...
For the person who fixes #4720 - when...
rather amusing...
@bsclifton - can we close this one too?
@mrose17 I don't think so. #6047 focuses on the UI change.
@mrose17 reading through your commit I'm still not sure how I can differentiate between a network error and a failed recovery (bad keys). Can you help me understand how to do this UI work?
Thanks!!
@mrose17 looks like @jkup needs some more info (he should be back next week)
I'm still not sure how I can differentiate between a network error and a failed recovery (bad keys). Can you help me understand how to do this UI work?
here is the answer: look at ledgerInfo.error.err if it is a STRING, then there is a data input or server error; if it is an object, e.g., { errorCode: -109 } then there is a network error.
It seems this is not fixed. I followed the same steps after restarting the browser but it did not work either
In my case, the breakage was a bit nuanced.
Without a network connection, the UI did nothing. No warning, no error, it just took my clicks and walked away.
When the network connection was restored, somewhere in the middle of my machine-gunning the control, the recovery keys were accepted.
cc @bsclifton
Moved to 0.13.3
Removing milestone for now and putting on backlog- we're tracking in Asana. Will update once we have prioritized
Closing at @mrose17 direction.
Most helpful comment
it shouldn't have been closed. i did the first part, but now it's up to you!!!