Skip to main content
September 21, 2026

BUG: Login item has two fields with designation "username"

  • September 21, 2026
  • 1 reply
  • 1 view

Two Login items in my vault each contain two fields with designation "username".
The desktop GUI shows and edits only the first. macOS/iOS AutoFill fill the first
(correct). The browser extension (Safari + Chrome) fills the last (stale/wrong).
The second field is only visible in the item JSON and cannot be edited or deleted
in the app.


So far my only workaround is recreating the items manually in the desktop app and archive the old ones.

{
"overview": {
"title": "localhost",
"ainfo": "api-11583-test",
"url": "http://localhost:8000",
"URLs": [
{
"u": "http://localhost:8000",
"l": "website",
"m": "default"
},
],
"ps": 100,
"pbe": 0,
"pgrng": false
},
"details": {
"fields": [
{
"value": "api-11583-test",
"id": "username",
"name": "username",
"type": "T",
"designation": "username"
},
{
"value": "...",
"id": "password",
"name": "password",
"type": "P",
"designation": "password"
},
{
"value": "api-11583-testg",
"id": "username",
"name": "username",
"type": "T",
"designation": "username"
}
],
"sections": []
},
"createdAt": "2026-09-09T17:42:53Z",
"updatedAt": "2026-09-21T12:15:22Z",
"faveIndex": 0,
"trashed": "N",
"templateUuid": "001",
"uuid": "6lq4kxcbdazagpvuuwffbrtica"
}

This one was was saved with an incorrect username that I edited directly after inital save/creation. Extension fills "api-11583-testg".

 

{
"overview": {
"title": ".... (verify)",
"ainfo": "guacadmin",
"url": "https://verify...",
"URLs": [
{
"u": "https://verify...",
"l": "website",
"m": "default"
}
],
"ps": 100,
"pbe": 84.24922180175781,
"pgrng": true,
"lh": {
"v": 1,
"h": [
{
"i": "hpf4lkc7owxh74px753f2bklhy",
"v": "ll52xhop3wtehddqcxensuqg6y"
}
]
}
},
"details": {
"fields": [
{
"value": "guacadmin",
"id": "",
"name": "",
"type": "T",
"designation": "username"
},
{
"value": "...",
"id": "",
"name": "",
"type": "P",
"designation": "password"
},
{
"value": "m.fleischer",
"id": "",
"name": "",
"type": "T",
"designation": "username"
},
{
"value": "✓",
"id": "",
"name": "",
"type": "C"
},
{
"value": "✓",
"id": "",
"name": "",
"type": "C"
},
{
"value": "✓",
"id": "",
"name": "",
"type": "C"
},
{
"value": "✓",
"id": "",
"name": "",
"type": "C"
},
{
"value": "✓",
"id": "",
"name": "",
"type": "C"
},
{
"value": "✓",
"id": "",
"name": "",
"type": "C"
},
{
"value": "✓",
"id": "",
"name": "",
"type": "C"
}
]
},
"createdAt": "2026-08-07T21:06:34Z",
"updatedAt": "2026-09-21T12:00:43Z",
"faveIndex": 0,
"trashed": "N",
"templateUuid": "001",
"uuid": "x7ldmx2chaah33bjr2j7udedpe"
}

Cannot remember the exact flow at creation, but perhaps similar. Extension fills “m.fleischer”

 

Pinned Reply By 1P_Dave

Hello ​@mafl2k! 👋

I’m sorry that you’re seeing an item with two different usernames, we’ve received other reports of this behaviour and our development team is investigating. While we’re investigating to find the cause of the issue, we’re also shipping an improvement (currently being tested in the latest beta version of 1Password in the browser - 8.12.28-25) where only the first username will be filled for cases like this. 

Re-creating the broken item is the best fix for the moment. We’ll update this thread when we have more to share. 

-Dave

1 reply

1P_Dave
1Password Employee
1P_DavePinned
1Password Employee
September 22, 2026

Hello ​@mafl2k! 👋

I’m sorry that you’re seeing an item with two different usernames, we’ve received other reports of this behaviour and our development team is investigating. While we’re investigating to find the cause of the issue, we’re also shipping an improvement (currently being tested in the latest beta version of 1Password in the browser - 8.12.28-25) where only the first username will be filled for cases like this. 

Re-creating the broken item is the best fix for the moment. We’ll update this thread when we have more to share. 

-Dave