search

cashubtc / eNuts

A Cashu wallet for Android and iOS 🥜🐿️
https://enuts.cash
GNU General Public License v3.0
189 stars 25 forks source link

Cash out using LN invoice can result in error #175

Closed KKA11010 closed 1 year ago

KKA11010 commented 1 year ago

While trying to cash out from a mint by pasting a lightning invoice, an error can occur. This has to be investigated further to determine if it is a bug indeed. Will address this problem asap and provide an update on this issue asap

KKA11010 commented 1 year ago

You can try one of the other options to cash out your funds as a temporary fix until this issue has been clarified (scan the invoce QR with the eNuts wallet or cash out to a LNURL)

If you are not able to cash out, please be patient for the upcoming releases which might introduce a fix

swedishfrenchpress commented 1 year ago

I'm also getting this error when I try to pay / cash out by entering an LNURL address. IMG_7596

callebtc commented 1 year ago

I get the same error when trying to pay to an LN address such as callebtc@ln.tips

KKA11010 commented 1 year ago

I get the same error when trying to pay to an LN address such as callebtc@ln.tips

Good to know, thanks for reporting! This is the first thing I will fix and include in 0.0.4 because it results in a very bad UX!

tomzacchia commented 1 year ago

Typing in my wallet of satoshi LN address worked. Pasting LN invoice still throws an error, hope this helps!

KKA11010 commented 1 year ago

I get the same error when trying to pay to an LN address such as callebtc@ln.tips

@callebtc for what I have found out while debugging is that the mint is responding with "Cashu: Could not make payment." or "Cashu: Payment failed: CLN method 'pay' failed with 'Ran out of routes to try after 1 attempt: see paystatus'.".

The client is sending the relevant data correctly (in both cases, invoice or ln address) and I guess this is some kind of ln routing issue in the ln payment process or whatever (mint error message is not precise).

I am showing the cashu error message now instead of a custom (translated) client message