[Bug]: On-chain send blocked by Lightning sync overlay after scanning address

[pwltr]

What happened?

Scanning a valid Bitcoin on-chain address succeeds, but the Send sheet displays the “Connecting to network” overlay indefinitely instead of showing the amount entry screen.

The node is running and the address is decoded successfully. The overlay appears because the wallet has Lightning channels but none are currently usable.

Expected behavior

After scanning a valid on-chain address, Bitkit should proceed to the on-chain amount entry screen. An unusable Lightning channel should not block an on-chain payment.

Steps to Reproduce

1. Use a wallet with at least one Lightning channel that is currently unusable or disconnected.
2. Confirm the node itself is running and the device has internet access.
3. Open the QR scanner.
4. Scan a valid Bitcoin on-chain address.
5. Observe the “Connecting to network” overlay instead of the amount entry screen.

Logs / Screenshots / Recordings

Logs confirm that:

• The QR code was scanned and decoded as an on-chain invoice.
• Bitkit selected the amount entry flow.
• The node lifecycle was Running.
• Connections to the Lightning peer repeatedly failed.

Bitkit Version

master

Device / OS

Android emulator (sdk_gphone16k_arm64)

Reproducibility

Always, while the wallet has channels but none are usable.

Additional context

This occurs on the dev/regtest environment.

SendSheet calculates shouldShowSyncOverlay globally when the wallet has channels but none are usable. The resulting SyncNodeView covers the entire Send flow regardless of whether the scanned payment is Lightning or on-chain.

The connection overlay should account for the selected payment method so Lightning channel availability does not block on-chain sends.