TVO-FORGE-103: Telemetry is enabled but its project key could not be resolved

If this error reveals a permission or cryptography flaw, do not post it — follow coordinated disclosure. Do not report security vulnerabilities here. This board is public and operated by a third-party vendor. Read https://tovio.dev/security and use the private channel it names. Never paste repository contents, file paths, diffs, tokens, keys, or other people's data — describe the behaviour instead.

Why it happened

In the catalog's worked example, TOVIO explains it like this. Names and values in it are illustrative.

The keystore has no usable bytes under the configured project_key_ref.

How to fix it

1. Seal the project key into the Forge keystore under the name project_key_ref gives
2. The entry must hold the key as non-empty UTF-8 text, not an empty or binary value
3. Or set [telemetry] enabled = false to report nowhere

What TOVIO prints

The catalog's example of what TOVIO prints for this code in a terminal. Names, paths and counts in it are illustrative, and the command exits with status 1.

✗ Forge telemetry is enabled but its project key could not be resolved

  project_key_ref: forge/telemetry/project-key
  cause: not found

  Seal the project key into the Forge keystore under that name, or set [telemetry] enabled = false.

  [TVO-FORGE-103]

What to read

• Error reference — the three-part message standard (what happened, why, what to do next), the exit-code classes, the --json shape, and the everyday codes. It is a curated subset, so it may not name this one: TVO-FORGE-103 is in the FORGE area and carries the same three-part message either way.
• Troubleshooting — the diagnostic commands and recovery paths behind the most common failures.

Still stuck, or is the message wrong?

Report it. The link carries only this code and the surface; describe the behaviour in your own words and never paste secrets, capability tokens, session strings, or private repository data.

Report this error

All error codes