op 2.3 via Connect broken

Hey XIII,

Thank you for reaching out to us!
If your automations worked before, and only fail now, it is likely that this is a regression with the 1Password CLI, since Connect did not release any new versions, in the past few days.
I have tried, using 2.3.0 (with a Connect backend), to read fields from sections, both with names and IDs, as well as sectionless fields, and I was not able to reproduce this issue. Can you please give us more details about your setup?
For example, the json structure of an item where you noticed this happening (with all the sensitive details concealed, of course) could help us a lot.
Have you noticed that reading fields from sections is consistently broken, or only in specific scenarios/for specific items or fields?
Please, also let us know anything else that you think would be relevant.

Looking forward to hearing from you!
Best,
Horia

• reading those fields with 2.3.0 is consistently broken
• I reverted to 2.2.0 on one of my machines and then I can read the fields fine (using Connect)
• please try a concealed (password) field in a section of a secure note (that's what failing for me with 2.3.0 & Connect only)

Might me more complicated:

• op://Automation/fastmail/webdav/password does fail
• op://Automation/fastmail/imap/password returns a password

Thanks for the additional details. I'll look a bit into it, and will post here any updates that I come across.

Best,
Horia

I don't know whether this is relevant, but I also noticed this when executing op item get fastmail --format=json:

• On MacBook Pro (via 1password.com): JSON with item info
• On Pi/router (via Connect): [ERROR] 2022/05/23 14:29:28 vault not found: (and nothing after that colon)

EDIT: probably not; same error with 2.2.0, while that does return the webDAV password

This is indeed a known bug, limitation of Connect: vault has to always be mentioned.
Please let us know if you notice anything unusual in the output of:

op item get fastmail --format json --vault <your-vault>

I'm opening a ticket now, to make sure a more useful error is being added.

Best,
Horia

In particular, can you please let us know if the webdav (that seems to be problematic, when retrieving) has a properly formatted UUID (i.e. 26 characters, digits and lowcase letters?)

Have you noticed any other fields that behave similarly? Do the items that exhibit these problems have anything in common? For example, have they been created with the same client?

Looking forward to hearing from you.

Best,
Horia

Looks like item and vault are case sensitive for Connect, but case-insensitive for 1password.com?

• vault Automation works for both
• vault automation works for 1password.com only

However, with the correct casing (or even when using the item id instead of the item title), I get this:
* On MacBook Pro (via 1password.com): JSON with item info
* On Pi/router (via Connect): either item Fastmail not found

It seems that there might be two bugs.

The bug that you described in your last reply is related to retrieving items. I was able to pinpoint the specific change that caused it, and will address it.

However, this does not seem to be linked to the inability to retrieve fields within sections. Am I correct to understand that you were able to reproduce this bug (erroring when retrieving fields in sections) both using Connect and 1Password as backend?

Looking forward to hearing from you.

Best,
Horia

Am I correct to understand that you were able to reproduce this bug (erroring when retrieving fields in sections) both using Connect and 1Password as backend?

No, so far fetching a field (webdav/password) value works fine using 1password.com, but fails using Connect.

(but a similar field imap/password in the same item works on both 1password.com and Connect...)