Wallet stuck synchronizing

[drcpu-github]

Describe the bug
One of my wallets seems to be stuck in some endless synchronizing loop for the last week. In the top left corner, it says SYNCING 0.00%, it shows a number of blocks it still has to synchronize, but that counter never updates (screenshot 1). It also does not show any transaction history.

Interestingly, the other wallets in my local installation do synchronize properly. I tried restarting Sheikah several times, I tried restarting my computer and I tried connecting to another node, but nothing changes. I cannot force a resynchronization using the settings menu (the option is disabled), presumably because the wallet thinks it's still synchronizing.

I started the wallet in debug mode on the command prompt to see what it was doing. It does connect to my local node and it actually downloads all blocks, but the UI is not properly updating. After letting it run for a while, I noticed on the command prompt it had caught up with the tip of the chain (so it was technically fully synchronized) and it also indexed all new incoming blocks, but the counter in the left never updates. I restarted Sheikah again and now it does show a different amount of blocks to synchronize (screenshot 2) and the balance in the top right has also updated. However, as you can see, it's still at 0.00% and nothing ever changes. Because the UI thinks the wallet is not synchronized, I can also not create any transactions.

I could obviously delete the wallet and reinstall, but I first wanted to file this issue and see if there is anything else I can do to solve or root cause the issue.

Screenshots

Desktop (please complete the following information):

• OS: Windows
• Version 1.11.3

[Anlihuha]

I have the same issue in my Sheikah Witnet wallet. The wallet attempts to connect to the mainnet network via node 20.126.70.77:21338. However, the wallet just keeps disconnecting. For me, the Resych option is grayed-out as well.

[Anlihuha]

OS: Windows 10
Wallet version: 1.11.3

[aesedepece]

@drcpu-github how long has this wallet existed for? Sounds like it could be missing a field introduced thereafter, and we may be not handling that case, leading to a JavaScript exception that precludes the wallet status component from rendering properly.

[drcpu-github]

I created it roughly six months ago.

[aesedepece]

For once I can see that it doesn't have a wallet name shown by the gravatar 🤔

[drcpu-github]

I cut out the wallet name and description as it contained some identifying details, that's not part of the UI bug. 😄

[Anlihuha]

It was created in October 2020. Believe it or not, after seeing that some people just restarted the wallet multiple times and it finally synched, the wallet actually pulled my tokens for the first time (after roughly 10 to 12 restarts). The wallet still has major issues though. My first synch after it pulled the balance had an ETA of 172 days. No computer issues on my side with regard to memory/speed with any other programs. I also viewed the wallet process running through my security software, showing it had pulled amounts of info many times. Thanks for your response!

…

Sent from my iPhone

On Oct 3, 2022, at 2:27 AM, aesedepece ***@***.***> wrote:  @drcpu-github how long has this wallet existed for? Sounds like it could be missing a field introduced thereafter, and we may be not handling that case, leading to a JavaScript exception that precludes the wallet status component from rendering properly. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.

[Tommytrg]

I've checked Sheikah's code and it needs to receive an event from the wallet server to be in syncing state. After the syncing event, it should receive new events such as SyncProgress or SyncFinish.

Maybe the wallet server is not sending the event with some wallets for some reason I still don't know. I'm going to continue debugging this and keep you updated

[Anlihuha]

Thanks a ton for the update. I appreciate it. From: Tomás ***@***.***> Sent: Monday, October 3, 2022 9:13 AM To: witnet/sheikah ***@***.***> Cc: Anlihuha ***@***.***>; Comment ***@***.***> Subject: Re: [witnet/sheikah] Wallet stuck synchronizing (Issue #1806) I've checked Sheikah's code and it needs to receive an event from the wallet server to be in syncing state. After the syncing event, it should receive new events such as SyncProgress or SyncFinish. Maybe the wallet server is not sending the event with some wallets for some reason I still don't know. I'm going to continue debugging this and keep you updated — Reply to this email directly, view it on GitHub <#1806 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKTNNZP2NIWTLEXUGKK47RLWBLZWRANCNFSM6AAAAAAQ2R5PIY> . You are receiving this because you commented. <https://github.com/notifications/beacon/AKTNNZKJDLZ7PTDKERQRBQTWBLZWRA5CNFSM6AAAAAAQ2R5PI2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSLN7E5C.gif> Message ID: ***@***.*** ***@***.***> >

[drcpu-github]

@Tommytrg Should I just try to delete the wallet and do a full resync to see if the issue happens again? If it does, it must be related to a specific block or transaction and that may help narrow it down.