What happened?
After migrating from React Native Bitkit to the native iOS app, custom Lightning channels (channels with non-LSP/custom nodes) are restored from backup, but the connection to the channel counterparty is not re-established. The channel state is present, but the app does not connect to the custom peer on startup, so those channels are not usable until the user manually reconnects.
Expected behavior
- On node start, the app should connect to:
- Trusted (LSP) peers (existing behavior), and
- Custom peers that either:
- have been used in this app (e.g. manual/LNURL channel) and were persisted, or
- were migrated from the RN backup (lightning state and/or
peers.json).
- After migration, custom channels should become usable without requiring the user to re-enter the node URI.
Steps to Reproduce
No response
Logs / Screenshots / Recordings
No response
Bitkit Version
master
Device / OS
iOS 26
Reproducibility
Always
Additional context
No response
What happened?
After migrating from React Native Bitkit to the native iOS app, custom Lightning channels (channels with non-LSP/custom nodes) are restored from backup, but the connection to the channel counterparty is not re-established. The channel state is present, but the app does not connect to the custom peer on startup, so those channels are not usable until the user manually reconnects.
Expected behavior
peers.json).Steps to Reproduce
No response
Logs / Screenshots / Recordings
No response
Bitkit Version
master
Device / OS
iOS 26
Reproducibility
Always
Additional context
No response