We recently encountered an issue where older versions of VVD (Vega Virtual Device) were incompatible with recent updates to Vega UI Components. As a result, if you use VVD for testing and depend on amazon-devices/kepler-ui-components, you need to use the latest VVD version included with SDK 0.22.
Each version of the Vega SDK comes with its associated VVD (Vega Virtual Device, a simulator running on your development machine) which aids in testing without a device, providing a fast development cycle. Like the devices running Vega, the VVD image is being updated with each release, so for instance the VVD provided with SDK 0.22 has native OS components that were not present in 0.21.
If you are using VVD to test your app, we recommend that you upgrade to the latest version of the SDK as soon as possible. You will then have the latest VVD, which will closely mirror the Vega device image deployed to Fire TV devices in the field, and you will avoid installation errors that come from missing dependencies.
We recommend also following npm best practices in checking lock files (like package-lock.json or yarn.lock ) into your source control to ensure repeatable builds.
FAQs
What if I cannot update the SDK version?
You can continue to use the physical device (FireTV Stick 4K Select) for testing assuming it gets regular updates from Amazon. Make sure your device is a release device (i.e. bought from Amazon.com) or if provided by your Amazon POC that it gets regular updates. This library was already deployed to the existing regularly updated physical devices. Alternatively, if you are on the 0.22.x SDK the Virtual Device can continue to be used or if you do not use the kepler-ui-components npm package, Virtual Device testing from older SDKs will still operate.
What error would I see if I run into this problem?
“/Users//myapp.vpkg”2026-01-20 16:45:08.646 [warning] Failed: Installing/Updating ‘/tmp/myapp.vpkg’ …error (Module dependency not found): error: Unable to install ‘/tmp/ppluskepler_aarch64.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
My app is built using an older SDK, but I want to test on Virtual Device, how do I do that?
Today your option is either to use the latest SDK or limit your testing to physical devices. The software for the physical device (FireTV stick) is newer (features, bug fixes, and api versions) than the virtual device included in older versions of the SDK. To get the most accurate test, we encourage app developers (internal and external to Amazon) to test on physical device. The Virtual Device is well suited to basic testing (including functional tests) as long as you keep it up to date (aka as of this writing in late 2026-Jan, 0.22.x). Older Virtual Device versions may yield inaccurate test results or encounter package conflicts.