You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
"When I try to send ecash to one of my nostr contacts, by pressing the send button in the contacts screen, it asks me to choose a mint (which is correct because I have multiple) and afterwards asks to chosse the send method (copy token or send via nostr). I press send via nostr and I am redirected to the contacts page where I press on the same contact again. it asks me again to choose a mint and I am stuck in this loop. Sending to nostr contact from my dashboard by pressing "send" works well tho"
To Reproduce
You will have to have multiple mints, so that the app asks which mint you want to send from
Go to 'contacts'
Press 'send'
Choose a mint
Press "Send over nostr"
See error
Expected behavior
It should be the following flow:
Go to 'contacts'
Press 'send'
Choose a mint
Type-in amount
Memo
payment overview
The text was updated successfully, but these errors were encountered:
Temporary workaround for poeple who are facing this issue: Send to a nostr contact by pressing "Send" in the dashboard > "Send Ecash" > select mint > "Send via nostr" > select contact > ... follow further steps provided by the app.
Describe the bug
"When I try to send ecash to one of my nostr contacts, by pressing the send button in the contacts screen, it asks me to choose a mint (which is correct because I have multiple) and afterwards asks to chosse the send method (copy token or send via nostr). I press send via nostr and I am redirected to the contacts page where I press on the same contact again. it asks me again to choose a mint and I am stuck in this loop. Sending to nostr contact from my dashboard by pressing "send" works well tho"
To Reproduce
You will have to have multiple mints, so that the app asks which mint you want to send from
Expected behavior
It should be the following flow:
The text was updated successfully, but these errors were encountered: