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: HJ Video app
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
-
make release build
-
install and launch app
-
Open VSCode -
Open Vega Launch App KPI Visualizer -> Application UI fluidity Test[check] -> Record CPU Profiler[check] -> Ignore trace loss[without check] -> Number of Iterations[3] -> For Application UI fluidity Test, do you want to use custom test scenario[No] -
kpi visualizer does not start
3. Observed Behavior
Explain what actually happened, noting any discrepancies or malfunctions.
kpi-visualizer started. Command: kpi-visualizer --kpi=ui-fluidity --output-dir=/home/tabuchi/IdeaProjects/hulu-kepler/generated --grpc-port=50051 --app-name=jp.happyon.android.main --device-serial-number=GT533M06507715E2 --test-scenario /home/tabuchi/IdeaProjects/hulu-kepler/appium/ui-fluidity-test.py --record-cpu-profiling --sourcemap-file-path=/home/tabuchi/IdeaProjects/hulu-kepler/build/debugging/Debug/srcmap/87fd69d49536693632e802a9955d019d41a22a5842b53549ea9bb82321b1fe3d.bundle.map --iterations=3
Running Command: Application UI fluidity Test
kpi-visualizer: Data successfully appended to file
kpi-visualizer: WARNING: All log messages before absl::InitializeLog() is called are written to STDERR
I0000 00:00:1771317567.564328 1549836 fork_posix.cc:75] Other threads are currently calling into gRPC, skipping fork() handlers
kpi-visualizer: vega exec perf <command> [options] [parameters]
: error: argument : invalid choice: 'tracker_fd=8' (choose from 'activity-monitor', 'record', 'kpi-visualizer', 'memory-monitor', 'generate-test-template', 'doctor')
kpi-visualizer exited
kpi-visualizer: /home/tabuchi/vega/sdk/vega-sdk/main/0.22.5600/packages/KeplerPerfCLI/KeplerPerfCLI-2.0.82.0/AL2_x86_64/DEV.STD.PTHREAD/build/x86_64-Linux/lib/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 3 leaked semaphore objects to clean up at shutdown
kpi-visualizer closed
4. Expected Behavior
Describe what you expected the SDK to do under normal operation.
kpi visualizer starts
4.a Possible Root Cause & Temporary Workaround
check appium path
$ which appium
/home/tabuchi/.nvm/versions/node/v22.14.0/bin/appium
$ vega exec appium --version
dbug Appium Parsed manifest file at /home/tabuchi/.appium/node_modules/.cache/appium/extensions.yaml: {
dbug Appium "drivers": {
dbug Appium "kepler": {
dbug Appium "pkgName": "@amazon-devices/appium-kepler-driver",
dbug Appium "version": "3.30.0",
dbug Appium "installType": "npm",
dbug Appium "installSpec": "@amazon-devices/appium-kepler-driver@3.30.0",
dbug Appium "installPath": "/home/tabuchi/.appium/node_modules/@amazon-devices/appium-kepler-driver",
dbug Appium "appiumVersion": "^2.2.2",
dbug Appium "automationName": "automation-toolkit/JSON-RPC",
dbug Appium "platformNames": [
dbug Appium "Kepler"
dbug Appium ],
dbug Appium "mainClass": "KeplerDriver"
dbug Appium }
dbug Appium },
dbug Appium "plugins": {},
dbug Appium "schemaRev": 4
dbug Appium }
2.2.2
check appium version and drivers
$ appium --version
dbug Appium Parsed manifest file at /home/tabuchi/.appium/node_modules/.cache/appium/extensions.yaml: {
dbug Appium "drivers": {
dbug Appium "kepler": {
dbug Appium "pkgName": "@amazon-devices/appium-kepler-driver",
dbug Appium "version": "3.30.0",
dbug Appium "installType": "npm",
dbug Appium "installSpec": "@amazon-devices/appium-kepler-driver@3.30.0",
dbug Appium "installPath": "/home/tabuchi/.appium/node_modules/@amazon-devices/appium-kepler-driver",
dbug Appium "appiumVersion": "^2.2.2",
dbug Appium "automationName": "automation-toolkit/JSON-RPC",
dbug Appium "platformNames": [
dbug Appium "Kepler"
dbug Appium ],
dbug Appium "mainClass": "KeplerDriver"
dbug Appium }
dbug Appium },
dbug Appium "plugins": {},
dbug Appium "schemaRev": 4
dbug Appium }
2.2.2
check performance doctor
$ vega exec perf doctor --app-name=jp.happyon.android
Data successfully appended to file
√ Firmware: Stable build (callie-user OS 1.1 (TV Ship day60/91)).
! Network: Not connected. Please check Wi-Fi settings on the target device
√ Free disk space: 254.59 GB available.
√ Appium: Installed (version 2.2.2)
√ Appium driver for Kepler: Installed - kepler@3.30.0 [installed (npm)]
√ jp.happyon.android is installed.
Collecting CPU (4 cores) and Memory data...
X Max User CPU usage at 320.00%. Check for unwanted processes.
√ Max System CPU usage at 100.00%
X Average User CPU usage at 230.68%. Check for unwanted processes.
√ Average System CPU usage at 36.16%
√ Min memory available at 38.52%
√ Average memory available at 38.72%
! Device: Not ready for performance testing. Please review lines with X (error) and ! (warnings) symbols.
check adb path
$ adb --help
Android Debug Bridge version 1.0.41
Version 36.0.0-13206524
Installed as /home/tabuchi/Android/Sdk/platform-tools/adb
Running on Linux 6.8.0-94-generic (x86_64)
5. Logs or crash report
- For issues with Vega Studio Extension, please share log files from below folders:
For v0.22+:
$ less ~/.vscode/extensions/amazon-devices.kepler-studio-0.22.2-linux-x64/ExtensionLogs
/home/tabuchi/.vscode/extensions/amazon-devices.kepler-studio-0.22.2-linux-x64/ExtensionLogs: そのようなファイルやディレクトリはありません
6. Environment
Please fill out the fields related to your bug below:
-
SDK Version:
$ vega --version Active SDK Version: 0.22.5600 Vega CLI Version: 1.2.18 -
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 found
$ vega exec vda shell
##################################################
##### Welcome to Developer mode Shell #####
##################################################
sh(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/91)"
BUILD_FINGERPRINT="4.0.216859.0(3072cab629675a74)/91N:user/release-keys"
BUILD_VARIANT="user"
BUILD_TAGS="release-keys"
BUILD_DATE="Wed Jan 28 22:43:49 UTC 2026"
BUILD_TIMESTAMP="1769640229"
VERSION_NUMBER="1401010009120"
Additional Context
- host OS information
$ cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.5 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.5 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy