nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 the error message above the invoice shows up while I'm connected to Alby, should only show up on embedded I assume?

nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 the error message above the invoice shows up while I'm connected to Alby, should only show up on embedded I assume?

Another thing, when I'm connected to alby's Lndhub obviously an onchain balance isn't possible, could the onchain part in this ss be hidden?

Also switching from Alby back to embedded node gets the app stuck on this screen(android) and I have to force close and load again for app to continue working

This is a tricky one because some LNDHub backends do support on-chain functionality.
Ah okay maybe lndhub itself needs an update that will pass a boolean value whether the wallet enables on chain or notπ€
Got a workaround for now. We maintain a list of hosts/patterns to identify which backends donβt support it.
LNDHub protocol is a mess. Crazy how so many people have built upon it and implement things in different ways.
Maybe just hide the button if the value is NaN? π€
Patched. Will be fixed in the next build.