Bug report: 'Import from CSV' doesn't set the 'URLs' field of items, breaking autofill feature

imtsuki
imtsuki
Community Member

Recently I decided to migrate to 1Password from iCloud Keychain. Following the official steps, I exported all my passwords from iCloud Keychain, and imported the CSV file into 1Password. However, I noticed that no matter which website I'm visiting, 1Password browser extension always shows a 'No items to show' popup where it's supposed to be autofilled:

At first I suspected this might be caused by some differences of URL matching rules, but soon I found that if I manually create an item, it will correctly show up in the autofill popup menu no matter how weird the URL is. These two versions (manually created and imported) look identical through 1Password GUI (8.8.0, macOS):

However, if you use the CLI tool, you can easily spot the difference. The manually created version has an URLs entry, whereas the imported version doesn't:

After some testing, the 1Password browser extension seems to only recognize those items that have an URLs entry.

Steps to reproduce:

  1. Export iCloud Keychain passwords from Safari. This should produce a CSV file that looks like this:
Title,URL,Username,Password,Notes,OTPAuth
example.com,https://example.com/,user@example.com,password,,
  1. Import the CSV file into 1Password. Then, visit any website via any browser, the browser extension won't suggest any imported items.

  2. Run op item get <name> in command line, and there will be no URLs in the output.

  3. Manually edit any field of the item through GUI and save. Re-run the command in step 3, and the URLs entry shows up.

  4. Visit the website, and the autofill will work.


1Password Version: 8.8.0
Extension Version: Not Provided
OS Version: macOS 12.5
Browser:_ Not Provided

Comments

  • Hey @imtsuki:

    Thanks for letting us know about this. We're aware of this and we've fixed these imports in our nightly releases, so keep an eye out for it to make it to the beta and production builds.

    Jack

    ref: dev/core/core#16519

This discussion has been closed.