Manually adding contact: After setting name and hitting "OK", a second "OK" displays spurious "Add contact: pubkey first".
Which device are you using
LilyGO T-Deck Plus
Which Firmware are you using
v0.9.12
To Reproduce
Go to "Mgmt" -> "Contacts" -> "Manual add contact" -> "Add"
Paste a contact public key
Tap "OK"
Set a name
Tap "OK"
Tap "OK" a second time
Observe a popup message saying "Add contact: pubkey first"
Expected behaviour
If contact was already sucessfully added, leave the dialogue with a success message.
**Describe the bug**
Manually adding contact: After setting name and hitting "OK", a second "OK" displays spurious "Add contact: pubkey first".
**Which device are you using**
LilyGO T-Deck Plus
**Which Firmware are you using**
v0.9.12
**To Reproduce**
1. Go to "Mgmt" -> "Contacts" -> "Manual add contact" -> "Add"
2. Paste a contact public key
3. Tap "OK"
4. Set a name
5. Tap "OK"
6. Tap "OK" a second time
7. Observe a popup message saying "Add contact: pubkey first"
**Expected behaviour**
If contact was already sucessfully added, leave the dialogue with a success message.
<!-- github-sync-id:4308090307 -->
Manual add contact: fixed the name-entry OK flow so a successful add closes cleanly instead of leaving a second OK press to trigger a spurious pubkey-first error (#209).
fixed in v0.9.12.1:
- Manual add contact: fixed the name-entry OK flow so a successful add closes cleanly instead of leaving a second OK press to trigger a spurious pubkey-first error (#209).
<!-- github-comment-id:4322727936 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Describe the bug
Manually adding contact: After setting name and hitting "OK", a second "OK" displays spurious "Add contact: pubkey first".
Which device are you using
LilyGO T-Deck Plus
Which Firmware are you using
v0.9.12
To Reproduce
Expected behaviour
If contact was already sucessfully added, leave the dialogue with a success message.
fixed in v0.9.12.1: