# 
Bug Description
—
## 1. Summary
**App Name**: Zee5
**App Link on Amazon Appstore**: N/A (app is in development/testing, not yet published)
**Bug Severity**
- [x] Blocks current development
- [ ] Impacts operation of app
- [ ] Improvement suggestion
- [ ] Issue with documentation
- [ ] Other
While creating a Live App Test (LAT) in the Amazon Developer Console, the VPKG upload fails with an OS version validation error, even though `[os.version]` = `1.1` is the correct/required value for our target device (Fire Stick running OS 1.1), and the same manifest.toml validates successfully with 0 errors when run locally via `vpt validate` / `vega build` using SDK 0.23.8128.
```
Error: Validation failed with the following errors:
Error 1: [os.version] contains value(s) not in the OS Version registry.
-
min: ‘1.1’ is not minted
-
target: ‘1.1’ is not minted
Valid OS Versions: “1.2”, “2.0”
```
## 2. Steps to Reproduce
1. Build the app locally with Vega SDK 0.23.8128 / Vega CLI 1.3.4, targeting `manifest.toml` with:
```toml
[os.version]
target = “1.1”
min = “1.1”
```
2. Confirm the package builds and validates locally with 0 errors:
```
vega build --target armv7 --buildType Release --build-number
```
→ `manifest.toml is valid`, `manifest validation found 0 errors`, `.vpkg` created successfully.
3. Upload the resulting `.vpkg` (e.g. `kepler_armv7.vpkg`) via the Amazon Developer Console when creating a Live App Test (LAT).
4. The Developer Console’s server-side validation rejects the upload with the OS Version registry error shown above, listing only `“1.2”` and `“2.0”` as minted/valid OS versions — `“1.1”` is not accepted.
## 3. Observed Behavior
- Local SDK/CLI (0.23.8128 / CLI 1.3.4) validates `[os.version] = “1.1”` successfully with zero errors and builds a working `.vpkg`.
- Our physical test device (Fire Stick, `deviceName: G4N33M03351401DV`) is confirmed to be running Vega **OS 1.1** (verified via `vega device info` and `/etc/os-release` on-device — see Environment section).
- The Developer Console’s LAT upload validation uses a stricter/newer OS Version registry that no longer recognizes `“1.1”` as minted, only `“1.2”` and `“2.0”`.
- This creates a hard blocker: we cannot declare `os.version = “1.1”` (required to match our actual OS-1.1 device) without failing Console upload, but bumping to `“1.2”` would misrepresent device compatibility and (per local module-dependency validation) requires a `[[needs.module]] id = “/com.amazon.vega.os@IVega_1_2”` entry that our OS-1.1 device does not have installed, causing `vega device install-app` to fail with:
```
Unable to install ‘/tmp/kepler_armv7.vpkg’ as the required dependencies are not found on the device.
The following module dependencies declared in the application manifest are not found:
- /com.amazon.vega.os@IVega_1_2
```
- Additionally, the Fire TV Stick devices available with us have **not received an update to OS version 1.2 or 2.0**. As shown in the attached device screenshot, the device’s current OS version is 1.1, and the device itself reports that it is **up to date** (i.e., no pending OS update is available/offered to the device). This means we have no way to obtain a device on `“1.2”` or `“2.0”` to test against, since those OS versions have not been rolled out to our hardware yet — the Console is requiring a manifest `os.version` value that is currently unreachable on real, up-to-date devices.
## 4. Expected Behavior
The OS Version registry used for Developer Console / LAT upload validation should stay consistent with what local SDK tooling (`vpt validate`, `vega build`) accepts for a given SDK version. Specifically:
- `os.version = “1.1”` should either remain a valid/minted value in the Console’s registry (since it is still a supported, shipping OS version on real devices), or
- The local Vega SDK/CLI tooling should surface the same “not minted” validation error locally (at `vega build`/`vpt validate` time) instead of only failing at Console upload time, so this is caught earlier in the dev loop.
## 4.a Possible Root Cause & Temporary Workaround
**Possible root cause**: The Developer Console’s LAT upload validator appears to use a different (newer) OS Version registry than the one bundled with local Vega SDK 0.23.8128 / CLI 1.3.4, which still accepts `“1.1”`.
**Workaround attempted**: Bumping `[os.version]` to `“1.2”` satisfies the Console’s registry check, but then local install fails on our OS-1.1 test device due to the required `/com.amazon.vega.os@IVega_1_2` module dependency not being present on-device. There is no combination of `os.version` value that currently satisfies both the Console’s registry and successful installation on an actual OS-1.1 device.
No other workaround found — this is currently blocking LAT creation for testing on OS-1.1 devices.
## 5. Logs or crash report
N/A (this is a manifest/upload validation error, not a crash). Full Console error text is included in Section 3 above. Happy to attach `.vpkg` and full CLI build logs on request.
## 6. Environment
- **SDK Version:** `vega --version` → Active SDK Version: `0.23.8128`, Vega CLI Version: `1.3.4`
- **React Native Version:** `0.72.0`
- **App State:** N/A (build/upload-time issue, not runtime)
- **OS Information:** (`vega exec vda shell “cat /etc/os-release”` on test device `G4N33M03351401DV`)
```
NAME=“OS”
OE_VERSION=“4.0.0”
OS_MAJOR_VERSION=“1”
OS_MINOR_VERSION=“1”
RELEASE_ID=“14”
OS_VERSION=“1.1”
BRANCH_CODE=“TV Ship day60”
BUILD_DESC=“OS 1.1 (TV Ship day60/4460)”
BUILD_FINGERPRINT=“4.0.227617.0(3072cab629675a74)/4460N:user-external/release-keys”
BUILD_VARIANT=“user-external”
BUILD_TAGS=“release-keys”
BUILD_DATE=“Fri Feb 20 16:02:43 UTC 2026”
BUILD_TIMESTAMP=“1771603363”
VERSION_NUMBER=“1401010446050”
```
## 7. Example Code Snippet / Screenshots / Screengrabs
Relevant `manifest.toml` excerpt (full file available on request):
```toml
schema-version = 1
[os.version]
target = “1.1”
min = “1.1”
[package]
id = “com.zee5.amazon”
title = “Zee5”
version = “1.5.0”
```
**Device screenshot (attached separately)**: Shows the Fire TV Stick’s system settings reporting OS version `1.1` and the device stating it is up to date, with no pending OS update available.
—
## Playback Issues
N/A — not a playback issue.
—
## Additional Context
- Reference doc: [ Manifest [os.version] Section - Amazon Vega Docs ]( Manifest [os.version] Section - Amazon Vega Docs )
- Requesting clarification on whether OS 1.1 devices are still officially supported for LAT/Appstore submission, and if so, why the Console registry no longer mints `“1.1”` as a valid `os.version` value.
- If OS 1.1 is being deprecated, requesting guidance/timeline on migration path for apps still needing to support OS 1.1 devices during a transition period.
- Our available Fire TV Stick devices have not received an OTA update to `1.2` or `2.0` and self-report as up to date at `1.1`, so we currently have no way to test/reproduce against a device on a “minted” OS version.
