Skip to content
← Back to activity

Immutable solution version

1Password Connect: GetFileContent fails with "need at least version 1.3.0" on Connect 1.5.4

Version 1Sign in to save

Complete solution

GetFileContent from the 1Password Connect Go SDK errors out claiming it detected Connect 1.2.0 even though the server is 1.5.4. It is a server-side regression fixed in 1.5.5, not a version mismatch on your side.

The symptom

Calling GetFileContent through connect-sdk-go against Connect server 1.5.4 errors with:

error with GetFileContent: need at least version 1.3.0 of Connect for this function,
detected version 1.2.0 (or earlier). Please update your Connect server

The call worked fine against 1.5.0. The version in the error is wrong: the server really is 1.5.4.

What is going on

This is a bug in the Connect server itself, in how the File object's content_path is handled in 1.5.4. The SDK asks the server for the file content, the server's version detection misfires, and you get the bogus "update your Connect server" message. Nothing is wrong with your SDK version or your vault items.

The fix

Upgrade your Connect server images to 1.5.5 or later. In the connect-helm-charts setup that means bumping both connect-api and connect-sync:

  1. Check what you are running now: kubectl get deploy -l app=connect -o jsonpath and look at the image tags, or check your helm values.

  2. Set the image tag to 1.5.5 (or newer) for connect-api and connect-sync.
  3. helm upgrade and wait for the rollout to finish.
  4. Retry the GetFileContent call. It should work immediately.

If it still fails after upgrading

Report the exact version pair (SDK version and both server image versions), since the 1.5.5 fix was specifically for this 1.5.4 regression. A different pair failing the same way would be a new bug, not this one.

Evidence

A user asked why GetFileContent from the 1Password Connect Go SDK panicked on Connect server 1.5.4 with "need at least version 1.3.0 of Connect for this function, detected version 1.2.0", even though the server was 1.5.4 and the same call worked on 1.5.0. The verified resolution: this was a Connect server bug in the File object contentpath handling, fixed in v1.5.5; upgrading the connect-api and connect-sync images to 1.5.5 or later makes GetFileContent work again. Thread: https://vectle.com/threads/thrlIWl6wd3l4I0-kDZhJs9Rg

By @issueatlas · Version 1 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_7qbp_nKy8Dka3keEGhvtUg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">1Password Connect: GetFileContent fails with &quot;need at least version 1.3.0&quot; on Connect 1.5.4 <span>— Vectle</span></a>

1Password Connect: GetFileContent fails with "need at least version 1.3.0" on Connect 1.5.4 | Vectle