[Mobile] Channel closed unexpectedly on app launch

[dpad85]

Issue by fresheneesz
Thursday Dec 21, 2017 at 17:16 GMT
Originally opened as ACINQ/eclair#313

---

I opened eclair just now and then went to my home screen without doing anything in the app. I then got a notification that my channel had begun closing uncooperatively from my side (details say the close is "local"). It's disconcerting that my channel could close automatically without me initiating it.

Also the notification doesn't do anything when i tap it - I'd expect it to bring me into the app at least.

[irekzielinski]

got the same on one of my channels - I have not initiated the close. Funds were returned to BTC wallet after 144 confirmations. Not sure what's going on here. Would be great to have an access to a low level log for each channel directly from the app.

[Perlover]

I have same problem between Eclair wallet 0.3.1 and last versions of lnd
I described my problem there:
lightningnetwork/lnd#1161 (comment)
May be it will help ...

[stefanwouldgo]

Same here. Immediately on my first payment attempt I got "Cause of closing: one or more htlcs timed out: ids=0". Don't know if that was even before I tried to pay. Does eclair mobile open public channels? I hope not.

[carnhofdaki]

Is there any update on this? Any word from the developers? It makes Eclair-Mobile pretty unusable even on Testnet. This is random. Happened to me multiple times. There is nothing I can provide to trace it. I am started to think that it is caused by the "fee protection" option in settings, which is turned on by default.

Ideas?

[pm47]

Is there any update on this? Any word from the developers? It makes Eclair-Mobile pretty unusable even on Testnet. This is random.

Testnet is typically less usable than mainnet, always has been. My bet would be a spec violation by lnd at reconnection. They have fixed a few of them in the past 12 months, there are probably more.

There is nothing I can provide to trace it.

Of course there is: enable logging in the app and provide the logs. Give information about the node you were connected to. Do your part of the work so we can do ours.

I am started to think that it is caused by the "fee protection" option in settings

This fee protection is just a cap on routing fees when running the path finding algorithm. This is completely independent of local channels and can't possibly affect their stability.

[carnhofdaki]

@pm47 Thank you for comments. I appreciate them. I will post when I have some logs.