Client troubleshooting

“No server” or “run vsync login”

Sign in again and confirm the server address:

vsync login --server https://builds.example.com

For CI, verify that both VSYNC_SERVER and VSYNC_TOKEN are present.

Unauthorized or invalid token

The token may be mistyped, expired, or revoked. Ask an administrator to issue a new token. If you use Perforce, run p4 login -a and then repeat vsync login --p4.

Perforce login returns 401

• Confirm p4 is installed and on PATH.
• Run p4 login -a, not only p4 login.
• Confirm your client uses the same spelling of P4PORT configured on the server.
• Ask the administrator whether Perforce authentication is enabled.

No build root configured

Set one or pass an explicit output directory:

vsync root D:\builds
vsync fetch <build-id> --out D:\temporary-build

Build or stream not found

Check the selected game and platform. Stream names are scoped by game and platform, and versions are unique within that pair.

Interrupted download

Run the fetch again. Completed chunks remain in the cache and are reused. The old checkout remains intact until staging completes.

A checkout looks damaged

Fetch the same build again from the desktop app, or run vsync fetch against the managed destination. Vsync reconstructs the checkout from verified chunks.

Disk usage is too high

Inspect Settings in the desktop app or run vsync cache status. Delete unused checkouts separately from pruning or clearing the cache.