FWIW, I experienced your second issue (or something similar) when I unknowingly tried to receive before my existing channel was ready (i.e. it was still in the offline state).
nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 First major issue(s) with your wallet. Trying to provide some feedback. I had a large channel w you guys force closed, and it has been pending for 5 days. The sats I had show up in the on chain portion but are still pending 5 days later despite a confirmed tx already having been executed. Secondly, I had another open channel with another node and had plenty of inbound liquidity. I tried to send a Lightning transaction to my wallet via that channel, but the app forced a 10k sat fee on me and opened a new a channel. Why would that happen when there is plenty of inbound liquidity from another channel?
Discussion
I think it would be nice to have a warning in this scenario to let the user know to wait until any existing channel comes online in order to receive, instead of taking 10K sats and opening another channel.
It did pop up at the top, but I thought it was more of a warning if I didn’t have sufficient inbound liquidity, which I did, it would then open a new channel. Now I’m trying to send another Lightning transaction and it wants to open a new channel again.