[Bug]: App closes after 5 seconds

[thejokoono]

Describe the bug

Was able to set up the app and receive a payment. I was also able to create a lightning channel (that didn't credit me the correct amount, but that's another issue).

Now, when I open the app, it closes after around 5 seconds without any error code. It does not crash when I turn off my internet.

Reproduce

1. Open App
2. Wait 10 seconds

Screenshots / Recording

telegram-cloud-document-4-5976665558974729114.mp4

Operating system

Android 12

Bitkit version

v1.0.0

Log output

No response

[Darth-Coin]

I have the same issue, same OS.

[Darth-Coin]

I updated to v0.1.0.0-beta30
On Android 12 (LineageOS)
Appeared the message "wallet restored" but when I click on "get started" button the app crash and close, literally disappear instantly.

I tried also on another device with vanilla android12, same behavior.
I tried wiping the app from device and install fresh, this new beta version.
Restored with seed, app crash and close.

I tried disabling the wifi/internet.
App stays in "settings up your wallet". Of course, is trying to connect with the server, bu no connection.
In this moment is nothing more I can do.

This is also a crash error I got on another device Android 11 vanilla, trying to restore a previous seed.

[pwltr]

Is this still an issue for you on the latest version of Bitkit v0.1.0.0-beta35? If so please use the new Recovery feature to share your LDK logs here or dm me on Telegram (logs do not contain sensitive information). To export the log .zip file:

1. Close Bitkit
2. Start Bitkit
3. Tap the screen repeatedly until shortly after the logo disappears (it's a double tap until 500ms after splash screen, but you have to be fast)
4. Press Export Lightning Logs

[Darth-Coin]

@pwltr Thanks to remind me about the new update. Any updates should be also announced on the telegram group.

Yes, I installed the beta36 update, app is not longer crashing, it stays active, but is showing only the remaining few sats from onchain wallet. The LN channel opened with Blocktank it says inactive,
If I go to Settings - Advanced - LN node info, it says LDK node disconnected, Bitkit failed to inititalize the LN node.
In LN connections, is empty and should be a LN channel of around 98k sats.
Electrum server is connected, seems to be working well the connection.

Is it something more I can do to help you identify what is causing this issue?
My Bitkit nodeID is 030587afffaf646d768ef71ef46fe2cde422a81bc24c0695165ba15158b354210f (I save it first time I create this Bitkit node).

[pwltr]

@Darth-Coin Looks like LDK is having trouble starting. If restarting the app doesn't fix it please try to export the logs as described above and upload them here. In any case there is a chance your channel got closed by Blocktank due to inactivity and funds will show up in a few days.

[pwltr]

@thejokoono Can you confirm the app is not crashing anymore on the lastest patch? Then I'll close here (can open follow-ups for any other issues you're facing).

[Darth-Coin]

@pwltr Is not working as you described with repeatedly tapping the screen.
But I found the LN logs into Settings - Advanced - LN connections - Export logs.
See them attached here. Reading into those logs, seems that the LN node is not starting.

Regarding that Blocktank could close the channel, that should've be done long time ago, but I don't think they were closed.
If would be closed, it should appear in LN connections as closing, but is nothing.

If there is a limit of time a channel must be active, that should be informed to the user when will open the channel. I wasn't informed about that in any way.
bitkit_ldk_logs_1676386715295.zip

Anyways, we have progress, the app at least is not crashing :)
If you find out the channel for my nodeID, please consider to close it.
Let's start over this testing.

[pwltr]

Closing here.

@Darth-Coin Regarding the LDK node not starting please move any communication to #770.

[thejokoono]

Was able to open the app and type in my recovery phrase but immediately crashes again.

Please reopen the issue.

telegram-cloud-document-4-6026025938775445411.mp4