op version two can't 'get' certain records

Hi @ftpd:

Thanks for reaching out about this! To clarify, when you say some-id, do you specifically mean the UUID of an item, or the name you've given it? Let me know.

Jack

Both. I've tried with UUID and with the name (in "" if it contains spaces, of course).

Hi @ftpd:

Thanks for confirming. In that case, could you please reach out to us directly at support+forum@1password.com? Include your username: ftpd and a link to this thread: https://1password.community/discussion/136950/op-version-two-cant-get-certain-records#latest. Mention the trouble you're having, and we'll be able to take a closer look there. Thanks!

Jack

Sure, @Jack_P_1P. Should I do it from an e-mail associated to my 1Password account I'm having this problem on, or it doesn't really matter?

Hey @ftpd:

Emailing us from your 1Password account email would be best, thanks! 🙂

Jack

Consider it done! Thanks again for your quick reply.

You're very welcome! We'll be in touch soon!

Jack

Hi @ftpd, I'm sorry you're running into issues while migrating!

One thing that comes to mind that's also different between CLI v2 series and in v1 you had to configure accounts specifically for the CLI, independent of your accounts configured in 1Password 8. If you have the "Connect with 1Password CLI" configuration turned on, v2 will use the accounts configured in 1Password 8.

In case the item with "bad-id" is stored in an account configured in ~/.op/config, but not in 1Password 8, that could explain the behavior you're running into.

Could you check the following to determine if you're in this situation:
1. Do you have https://developer.1password.com/docs/cli/about-biometric-unlock turned on?
2. When searching for "bad-id" in 1Password 8, do the results include the item you're looking for?
3. Does cat ~/.op/config or cat ~/.config/op include any accounts that are not configured in 1Password 8? Please don't paste the output here directly, or redact the entries for "accountKey". This is your secret key that only you should know.

Hi @1P_Simon, thanks for your reply.

My op is not linked in settings - the documentation here: https://developer.1password.com/docs/cli/about-biometric-unlock/ says it's optional. I've added my account by op account add command and the config file in ~/.config/op/config looks fine.
Actually, I would like to stick to this configuration, as configuration via Polkit etc. can be troublesome for less technical people in my organization.

When I search bad-id (by UUID) in 1Password 8, I see the record just fine. Please note: all my records are stored in this account (in the same vault) and part of them works and part doesn't.

Okay, thank you for quickly ruling out the account configuration as possible culprit. Jack is continuing investigation into this inconsistency via the email thread you've started.