op 2.3 via Connect broken

Did not see it appear in my RSS feed yet (oh wait, that also does not work because of this bug), so thank you for informing me here.

CLI version 2.3.1 indeed solves the problem; I can now read that password using both 1password.com and Connect! Thank you!

Hey XIII

This should fix it: https://app-updates.agilebits.com/product_history/CLI2#v2030101
Thank you once again for raising this with us, and helping us diagnose and fix this.
Looking forward to hearing your feedback!

Best,
Horia

That's good news!

Hope the fix will be available soon; several automations are broken here because of this...

(apparently I got quit dependent on this new 1Password product;)

Indeed, we think we've identified it!
Thank you for all your help here.
We're currently working on a fix, and will notify you as soon as this rolls out!

Best,
Horia

I think the issue occurs because the field names in two sections of one item are identical...

This is what happens with different field names:

• webdav/password & imap/password: only reading imap/password works
• webdav/passwork & imap/password: reading both fields work
• webdav/password & imap/passwork: reading both fields work

Does this help in finding/fixing the bug?

I've looked a bit into the code responsible for this, and have confirmed that this error can be returned in two cases:

• the section cannot be properly identified
• the field cannot be properly identified

In order to continue diagnosing this, can you please take another look at your item's json and let us know if there is anything that appears unusual about the section/the field that this error happens for?

In particular, I am interested whether the field ID and the section ID (as they can be seen in the item's json format) are properly formatted: i.e. strings made out of 26 characters (lowercase letters and digits). My hunch is that there may be something off with the validation that the CLI performs when passing queries to Connect, when looking up sections/fields.

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...)

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

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

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