VAST error codes / Parsing and schema
VAST error 102: VAST version not supported
Short answer: The player does not support the VAST version declared on the response.
Debug this tag now
If you only have a live URL, test it first. If the failure is in the wrapper chain, inspect each hop. Validate resolved XML when you already have the response.
What your player reported
102· VAST version of response not supported.
Wording from the IAB VAST 4.3 specification error table. Players may shorten or reformat it, but the code is the same.
What it means
The `version` attribute on `<VAST>` names a version the player will not render: too new, or malformed.
Common causes
- `version` attribute missing or not a recognised value (2.0, 3.0, 4.0–4.3)
- A 4.x response sent to a player that only supports 3.0
- Version on the response does not match what the chain negotiated
How to fix it
Confirm the `version` attribute is present and a value the player supports, and that wrapper and inline versions are consistent.
VAST error codes are runtime buckets emitted by the player. They tell you where the failure happened, not which line of XML caused it. Paste the raw tag into the validator to map this code onto the exact element and rule.
Related vastlint rules
- VAST-2.0-root-version: <VAST> must have a version attribute
- VAST-2.0-root-version-value: VAST version attribute must be a recognised version string
- VAST-2.0-version-mismatch: Declared version does not match structural signals
Related error codes
Debug this tag now
Validate the XML, follow the wrapper chain, or check it in CI before launch:
# CLI: exits non-zero on errors, ideal for pipelines
vastlint check creative.xml