Channel closing (uncooperative) - no progress in status even after 144 blocks

[griswaalt]

So I set up a channel with the SLEEPYARK node to buy some blockstream stickers. However, since my funding amount was a bit less, I couldn't make a purchase tx so I decided to close the channel. On clicking close, the status changed to closing (uncooperative) and there has been no progress since then. I closed the channel over 2 days back so it is well past 144 blocks. However, there is no on chain tx to return my funds and I see the status as closing (uncooperative). Any ideas what could be the issue?

[gustavocoding]

Identical to #17
Unfortunately I was not lucky to get logs and figure out the exact cause, but it's a good thing it can be reproduced easily so devs will be able to fix

[pm47]

@griswaalt @gustavonalle Any of you has a rooted phone? Being able to access app data would facilitate debugging a lot

[griswaalt]

@pm47 I am running this on stock, unrooted Android.

[gustavocoding]

@pm47 If you run the app in the android studio using the emulator in debug mode, put 2 mBTC, wait for confirmation, open a channel to a node you control, kill that node, forcefully close the channel in the emulator, you'll probably be able to reproduce the issue, since pretty much everyone is seeing it.

Now, since you lost the password to update the app on google play (https://twitter.com/acinq_co/status/982749523104673792), the question is if it's possible to manually create a tx to redeem the funds stuck in the wallet or create a script/app to do so...

[pm47]

Yes we are doing that, but the more information the better

the question is if it's possible to manually create a tx to redeem the funds stuck in the wallet or create a script/app to fix the issue...

Not without the app data, because there is per-channel random data that is generated by each peer for each channel

[gustavocoding]

Not without the app data

You mean not without rooting the phone and reading the SQL DB?

[pm47]

Not without the app data

You mean not without rooting the phone and reading the SQL DB?

Yes

[gustavocoding]

Hmmm...that's bad :(

What if I build the app directly from (bug fixed) sources and manually install it on the phone?

[pm47]

What if I build the app directly from (bug fixed) sources and manually install it on the phone?

If you do that, signature will be different and android will reinstall the app, deleting the data in the process :-/

[gustavocoding]

I can see you also have android:allowBackup="false" in the Android manifest, which would prevent obtaining the data via a backup with the user permission 😭

[pm47]

Yes, this is by designed. The app data is completely locked from the inside

[dognip]

So it sounds like either we root our phones or we lose the funds? Is that correct?

[pm47]

We don't know yet, I haven't even been able to reproduce the issue. As soon as we understand exactly what the problem is, we'll be able to tell

[pm47]

This is a duplicate of #17, please see updates there.