search

nbd-wtf / obw

Open Bitcon Wallet (OBW) is a lightweight Android Bitcoin and Lightning wallet
Apache License 2.0
117 stars 16 forks source link

Channel stuck at the opening stage. #33

Open sneakingweasel opened 1 year ago

sneakingweasel commented 1 year ago

Recently tried to open my first channel, it seems the on-chain tx broadcast fine but the channel is stuck at the opening stage despite hundreds of on-chain confirmations. I have network activity displayed at the taksbar in Android which doesnt show any activity after the initial chain sync upon opening the app. It seems like LN connectivity is broken for me. Already tried to close the channel but nothing happens, tor doesnt work either.

[Lineage 19.1, Android 12]

fiatjaf commented 1 year ago

This has happened to me multiple times when opening a channel to LND. The channel is missing a message from either OBW to LND or vice-versa. Weirdly, when trying to debug once it looked like the problem was with OBW, others it was with LND. After a while and a couple restarts the message always does get sent though, and the channel works, still unclear triggered by what.

sneakingweasel commented 1 year ago

I see, not just me then. I have opened the app probably 10 times a day for 4 days now but the channel has never worked. Is there any way I can dump a log file from the app to help get this fixed? I'm completely stuck and would like to use this LN wallet.

In the meantime, I guess force-closing the channel to at least regain control over my funds is the best thing to do...

If you don't mind, can you tell me which node you're connected to that works?

fiatjaf commented 1 year ago

Sorry for the lack of responses here. Did this have any other development? Did you force-close?

sneakingweasel commented 1 year ago

No worries.  Yes, I managed to force close the channel and get the funds out of OBW.  The "delayed channel refunding" notification remained for days after though so I think we have another bug there.

Since the latest update (0.2.1-12) I noticed that the "channels" sync bar is now displayed upon opening the wallet.  However, I have tried to open another channel and I have the same issue as before.  The tx has hundreds of confirmations, the channel sync bar no longer appears when I open OBW and I still cannot perform any LN transactions.  The channel is stuck in the opening stage with no active connection to the other peer.

31 Dec 2022, 8:15 pm by @.***:

Sorry for the lack of responses here. Did this have any other development? Did you force-close?

— Reply to this email directly, > view it on GitHub https://github.com/nbd-wtf/obw/issues/33#issuecomment-1368214448> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/A4YRBTEE6GICGK4M2LNMPJLWQAWXNANCNFSM6AAAAAAS7Y2WMA> . You are receiving this because you authored the thread.> Message ID: > <nbd-wtf/obw/issues/33/1368214448> @> github> .> com>

fiatjaf commented 1 year ago

Thank you very much. I'm keeping this in mind. This issue will be fixed, but I can't give you a date for that. Maybe you should stick to SBW for now.

Darth-Coin commented 1 year ago

I have the same situation. OBW 0.2.1.-12, fresh install, opened a channel with a LND node, tx confirmed, on the LND node side the channel appear as online, but in my OBW is in "opening" state. I opened using clearnet node URI and also using OBW in clearnet, no Tor.

SkanderHelali commented 1 year ago

Can confirm. Channel stuck 'opening' despite hundreds of confirmations. Had to force close. Force close wouldn't sweep after the required block delay and stuck in 'waiting' for hundreds more blocks.

OBW would become slow, and crash with variations of this:

java.lang.OutOfMemoryError: Failed to allocate a 5240 byte allocation with 31696 free bytes and 30KB until OOM, target footprint 536870912, growth limit 536870912; giving up on allocation because <1% of heap free after GC.

Phone has plenty of RAM available.

Restored with OBW's backupfile + seed to SBW and it immediately swept the FC funds. Something is (very) broken. I'd try to warn against using OBW for anything other than onchain and HCs for the time being.

Edit: peer was CLN btw, so not an LND<->OBW issue.