Restore onchain wallet stuck - Android

Darth-Coin commented 3 years ago

Environment:

devices: Android 8.1 (LG), Android 11 (Motorola G9), Android 7 (Galaxytab A tablet)
software: Blixt v.0.3.9

Actual behavior / case:

had a previously new wallet on LG Android 8.1, no LN channels
Blixt was synced (checked logs)
sent some sats like 160k into onchain address (one that appear on main screen), confirmed in mempool
meanwhile waiting for confirmations I switched to Tor to see how it works and check the Tor onion address node URI
Tor onion URI never show and also I had to force close the app, because it wasn't restarted after Tor activation (as should be)
in Blixt never shown the funds arrived
switched back to clearnet, let the wallet to sync
Neutrino says all blocks are synced but in logs seems that rescan addresses are stuck on block 675952 (or something like that) - see logs attached for android 8.1

Steps that I did:

Recover in another phone A

on another phone Motorola G9 Android 11 I installed new Blixt
recover from seed, wait few mins to sync, checked the node id to be same
all funds recovered, shown in onchain wallet
tested a bit with Dunder, sending 2 LN payments to Blixt
channels were open perfectly fine
send some test LN payments, all OK, smooth
switched to Tor, app restarted, took a while to start Tor
Tor onion address shown perfectly
tested adding as peer in another node, works perfectly
send out all funds from onchain, to see if pushing a new tx will do the rescan in the old phone
funds sent correctly
old phone do not "detect" any new tx.

Forced clear logs/data:

go to settings, change name to Hampus
go to dev screen - Callee04
clicked on DEBUG_DeleteWallet and actions.clearApp, confirmed for both that data will be lost
restart app
first screen was to restore wallet (so all data was deleted, not just logs and sync)
ok, so I tried restore from seed only (no channels)
get error message: error reading from server EOF
force closed app and uninstall it (but I forgot to check if any of dust files remained)
installed again the app
restore from seed only, same error
force closed app
tried again and now it says: closed and nothing else

Recover in another phone B

on another device, a GalaxyTab A with Android 7 (yeah old)
install new Blixt, recover fro,m seed (clearnet) - done
checked the node id in settings - node information, all OK same ID
wait a few minutes to finish the sync, checking the logs
took a bit more time than Android 11, but in then end all onchain txs appeared (balance 0 because were sent all out)
see attached lnd logs for galaxytab-android

Logs files attached lnd-mainnet-android-8-11.log lnd-mainnet-galaxytab-A-android7.log

Observations:

I think on Android 8.1 it get stuck at that specific block (but is not the block with the tx) and is not scanning for more txs/addresses anymore even if the sync says that get the latest block

Desired behavior:

I want to be able to use Blixt on that Android 8.1 and recover full wallet + LN channels (I have a backup now of the channels)
What will be the standard procedure to restore full wallet (seed + channels). Is it possible to not close those channels in the process or it depends on LND limitations?
This case can be a testing ground to detect more issues or improve the process. Willing to help.

Darth-Coin commented 3 years ago

Did another test today:

Erased Blixt from phone with Android 8.1
install fresh from Play Store - restore seed only
sync went to latest block
rescan blocks for addresses stopped at height 697151 (every time stop to this block)

Here last part of the lnd logs: 00:02:01.137 [INF] CHRE: LightningWallet opened 00:02:01.152 [INF] HSWC: Cleaning circuits from disk for closed channels 00:02:01.152 [INF] HSWC: Finished cleaning: no closed channels found, no actions taken. 00:02:01.152 [INF] HSWC: Restoring in-memory circuit state from disk 00:02:01.155 [INF] HSWC: Payment circuits loaded: num_pending=0, num_open=0 00:02:01.177 [INF] LTND: Channel backup proxy channel notifier starting 00:02:01.177 [INF] ATPL: Instantiating autopilot with active=false, max_channels=5, allocation=1.000000, min_chan_size=20000, max_chan_size=16777215, private=true, min_confs=1, conf_target=3 00:02:01.178 [INF] LTND: We're not running within systemd 00:02:01.179 [INF] LTND: Waiting for chain backend to finish sync, start_height=708399 00:02:02.030 [INF] RPCS: New transaction subscription 00:02:02.150 [INF] BTCN: Registering block subscription: id=2 00:02:02.155 [INF] LNWL: Started rescan from block 0000000000000000000efcb5071de099829de5ddac9713da4fca9ae6ae8de01d (height 697150) for 1 address 00:02:02.156 [INF] BTCN: Canceling block subscription: id=2 00:02:02.179 [INF] LNWL: Catching up block hashes to height 697151, this might take a while 00:02:02.190 [INF] LNWL: Done catching up block hashes 00:02:02.191 [INF] LNWL: Rescanned through block 0000000000000000000c2b06a6ce90c93e496263a537521b5755f68c5c6f65cb (height 697151)

Darth-Coin commented 3 years ago

New update testing: Not sure if is related, but worth mentioning. Blixt v 0.3.11 I did a recent test with GalaxyTab tablet (Android 7), switching to SPV server on my Umbrel local server. It get stuck in sync, even from local IP. So no sync in logs. I switched back to SPV server node.blixtwallet.com (also tried with blank). It sync the blocks, then the line for rescan appear

Rescanned through block .... (height 708375) for 3 addresses Canceling block subscription: id=2

And stays like that forever. Onchain transactions log is lost, all txs that were there before are gone, balance is 0.

hsjoberg / blixt-wallet