Repository navigation
"Editing is not supported for unsupported fields" #207
Description
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
Activity
ulope commentedon Sep 15, 2026
I'm having exactly the same issue for exactly the same use-case.
Also I'm wondering why the sdk forces a complete item rewrite? Why not allow updating single fields atomically?
benperry6 commentedon Oct 16, 2026
We can reproduce a matching error with the official JavaScript SDK (
@1password/sdk@0.5.0) on a headless Linux VPS using a service account. I am adding this here because the error matches; I have not established that the internal cause is identical across the SDKs.Our diagnostics on one existing Login item found:
Editing is not supported for unsupported fields.The operational requirement is to add ordinary concealed credentials to the existing item, programmatically, while preserving all unrelated content, including any passkeys. Recreating the item or serializing only the exposed fields would not meet that requirement.
Could a maintainer confirm how to diagnose the unsupported content, and whether there is a supported programmatic update method that preserves it? If this is a known defect, please link the tracking issue and any fixed SDK version. We can provide a sanitized reproduction privately through support.