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.
App Name:
App Link on Amazon Appstore (found through Developer Console → Actions column in App List → View on Amazon.com):
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
There was no specific steps that led to this, i think maybe when i installed“@amazon-devices/react-linear-gradient”: “^2.0.0”,
3. Observed Behavior
Explain what actually happened, noting any discrepancies or malfunctions.
Kepler operation FAILED due to an irrecoverable error: Failed to install build/x86_64-debug/vegatvapp_x86_64.vpkg on device VirtualDevice: Failed: Installing/Updating '/tmp/vegatvapp_x86_64.vpkg' ...error (Module dependency not found)
: error: Unable to install '/tmp/vegatvapp_x86_64.vpkg' as the required dependencies are not found on the device.
The Kepler Virtual Device is missing modules that are available on a physical device. Test your app using a Fire TV Stick instead.
The following module dependencies declared in the application manifest are not found:
- /com.amazon.kepler.native_ui_components_2@INativeUiComponents_13
4. Expected Behavior
Describe what you expected the SDK to do under normal operation.
i expected to run the build on the emulator and continue develpoment
4.a Possible Root Cause & Temporary Workaround
Fill out anything you have tried. If you don’t know, N/A is acceptable
<!-- Answer here -->
5. Logs or crash report
(Please make sure to provide relevant logs as attachment)
For crash issues, please refer this guide for faster troubleshooting: Detect Where the App Crash Originates | Design and Develop Vega Apps
-
For issues with Kepler Studio Extension, please share log files from below folders:
kepler-2026-01-15.log (38.2 KB)
6. Environment
Please fill out the fields related to your bug below:
-
SDK Version: Output of
kepler --versionActive SDK Version: 0.21.5245
Vega CLI Version: 1.2.7 -
App State:
[Foreground/Background] -
OS Information
Please ssh into the device viakepler exec vda shelland copy the output fromcat /etc/os-releaseinto the answer section below. Note, if you don’t have a simulator running or device attachedkepler exec vda shellwill respond withvda: no devices/emulators foundkvd-tv:/$ cat /etc/os-release NAME="OS" OE_VERSION="4.0.0" OS_MAJOR_VERSION="1" OS_MINOR_VERSION="1" RELEASE_ID="10" OS_VERSION="1.1" BRANCH_CODE="TV Ship" BUILD_DESC="OS 1.1 (TV Ship/10240280)" BUILD_FINGERPRINT="1.0.24028.0(c449c30bb1fb0cc8)/10240280N:user/dev-keys" BUILD_VARIANT="user" BUILD_TAGS="dev-keys" BUILD_DATE="Thu Sep 25 10:31:39 UTC 2025" BUILD_TIMESTAMP="1758796299" VERSION_NUMBER="1002034028030"
7. Example Code Snippet / Screenshots / Screengrabs
Include any relevant code or component setup in React Native that can help reproduce the bug.
import { ExampleComponent } from 'custom-sdk';
<ExampleComponent config={{ key: 'value' }} />
Playback Issues
If this is a playback issue, please provide your content URL, any pre-conditions (like geo-location), and let us know if it’s x86 or arm7.
<!-- Describe your playback issue if applicable -->
Please share the following details in addition:_
- Player SDK:
[Bitmovin, Shaka, ...] - Player SDK Version:
[e.g. 1.23]- Audio Codecs:
[AAC, ...] - Video Codecs:
[h.264, mp4] - Manifest Types:
[m3u8, dash, etc ..]
- Audio Codecs:
Q: If applicable, please provide your media/content url
If this is created dynamically, tokenized, etc please provide a way for us to access it
[N/A or Content / Media Url for testing]
Q: Are there any special headers required to reproduce the issue you are facing?
[N/A or Insert Headers]
Additionally please provide the following if possible
Provide Screenshots / Screengrabs / Logs. Please include as much information as you can that will help debug.
<!-- Answer here if applicable -->
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.
I tried deleting node_modules and reinstalling everything, and I also reinstalled the SDK, but nothing fixed the issue.
I read the forum threads about this bug and saw that it was related to changing the SDK version and an @amazon library that was not supported by the new SDK. However, this error did not appear during the SDK upgrade, and after checking my package.json, all the libraries seem to be compatible with the current SDK version.
What is confusing is that I was working on a new feature in a separate branch when this started happening. When I switched back to an older version of the code (which previously worked), the same error still occurs. That makes it seem like something in the environment or SDK setup is broken rather than the code itself.
Here is a link to my project: