Before you continue
Before submitting a bug report, please review our troubleshooting documentation at Troubleshoot Issues | Vega Troubleshooting
If you still want to file a bug report, please make sure to fill in all the details below and provide the necessary information.
NOTE: PLEASE ONLY REPORT A SINGLE BUG USING THIS TEMPLATE.
If you’re experiencing multiple issues, please file a separate report for each.
Bug Description
1. Summary
Provide a brief description of the bug in the SDK and its impact on app functionality.
After some testing in different TimeZones, we have found some missmatching between the starttime and endtime for the same program in different countries.
App Name:
VIX
Bug Severity
Select one that applies
- Impacts operation of app
- Blocks current development
- Improvement suggestion
- Issue with documentation (If selected, please share the doc link and describe the issue)
- Other
2. Steps to Reproduce
-
Open the ViX app.
-
Select EPG Live on the side menu.
-
Take a look at the hours of the asset.
-
Compare the time with the local time or with another platform, such as the Web
3. Observed Behavior
Explain what actually happened, noting any discrepancies or malfunctions.
The start time and endtime does not match the same times as the VIX Web for different timezones (countries)
4. Expected Behavior
Describe what you expected the SDK to do under normal operation.
The time should match the same on both platforms for the same timezone
4.a Possible Root Cause & Temporary Workaround
Fill out anything you have tried. If you don’t know, N/A is acceptable
Not sue
5. Logs or crash report
6. Environment
Please fill out the fields related to your bug below:
-
SDK Version: Run
vega --version(v0.22+)
Active SDK Version: 0.22.6150Vega CLI Version: 1.2.13
-
App State:
Foreground -
OS Information: Please ssh into the device via
vega exec vda shell(orkepler exec vda shellfor v0.21 and earlier) and copy the output fromcat /etc/os-releaseinto the answer section below. Note, if you don’t have a simulator running or device attached, the command will respond withvda: no devices/emulators foundsh(com.amazon.dev.shell):/$ cat /etc/os-release 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/102)" BUILD_FINGERPRINT="4.0.253712.0(3072cab629675a74)/102N:user/release-keys" BUILD_VARIANT="user" BUILD_TAGS="release-keys" BUILD_DATE="Fri Mar 20 21:10:28 UTC 2026" BUILD_TIMESTAMP="1774041028" VERSION_NUMBER="1401010010220"
Additional Context
Any Additional Context you would like to provide?
Add any other relevant information, such as recent updates to the SDK, dependencies, or device OS that may affect the bug.
For some other sections of the app we are setting the times using
.toLocaleString('en-US', { timeZone })

