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
After adding a contact, it can be used at several screens, and when you either select the contact or scan the contact's qrcode (address) it shows up in the UI, but then Kalium fails to send because it claims that the contact is invalid. Apparently there is validation for a BAN address at this point, and the text box contains the contact name. You are then required to remove the contact, or else every time you try to send to that BAN address, Kalium will recognize it is a known contact, and replace the contact name in the text box for the recipient address, and validation will again fail. Tested in v2.5.1.
I suggest always showing the BAN address, and just use another field to show the contact's name if it currently matches that address. Every final send screen should show the BAN address, for confirmation purposes.
The text was updated successfully, but these errors were encountered:
After adding a contact, it can be used at several screens, and when you either select the contact or scan the contact's qrcode (address) it shows up in the UI, but then Kalium fails to send because it claims that the contact is invalid. Apparently there is validation for a BAN address at this point, and the text box contains the contact name. You are then required to remove the contact, or else every time you try to send to that BAN address, Kalium will recognize it is a known contact, and replace the contact name in the text box for the recipient address, and validation will again fail. Tested in v2.5.1.
I suggest always showing the BAN address, and just use another field to show the contact's name if it currently matches that address. Every final send screen should show the BAN address, for confirmation purposes.
The text was updated successfully, but these errors were encountered: