"Editing is not supported for unsupported fields" #207

Scenario & Reproduction Steps

Hi there--I'm rewriting all of our entries that contain our main domain to use op.AutofillBehavior.EXACTDOMAIN to make 1Password usable for us (we have ~1,300 entries for all our services on various subdomains, so we get ~1,300 entries in the suggest box when we click into a login field).

However, just changing that one field fails on a bunch of the items, with the error message in the title.

When I look at the entry in 1Password, however, there are no unsupported fields. There's actually no fields set aside from the username, password, and website, e.g. the entries look no different than the entries where the call succeeds.

It does seem like the entries that fail are the earlier entries in the vault, so maybe they're too old in some way? Will saving those entries cause them to be updated?

Secondly, the rate limits make no sense. I manage to trigger them no matter how much delay I add, and then it's not clear how long I have to wait to continue. We're on a plan that predates Business but has some Business features. It has a 100/hr write rate limit instead of 1,000. Rate limit resets after 60 minutes. We're good. 👍

Here's an ID for one that failed to save due to unsupported fields:

5nyic4qdcpapcnk5npbhxyt3by

Actual Behavior

"Editing is not supported for unsupported fields"

Expected Behavior

Saves successfully.

SDK version

0.4.0b2

Additional information

No response