# KPI Visualizer does not working **URL:** \ **Category:** Bug Reports\ **Created:** [February 17, 2026, 6:34am UTC](https://community.amazondeveloper.com/t/kpi-visualizer-does-not-working/27696 "2026-02-17T06:34:46Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![nobuyuki.tabuchi](https://dhm3gbtzu79o6.cloudfront.net/user_avatar/community.amazondeveloper.com/nobuyuki.tabuchi/32/1916_2.png) [@nobuyuki.tabuchi](https://community.amazondeveloper.com/u/nobuyuki.tabuchi)\ **Post date:** [February 17, 2026, 6:34am UTC](https://community.amazondeveloper.com/t/kpi-visualizer-does-not-working/27696/1 "2026-02-17T06:34:46Z")
# ⚠ Before you continue * * * _Before submitting a bug report, please review our troubleshooting documentation at_ [Troubleshoot Issues | Vega Troubleshooting](https://developer.amazon.com/docs/vega/0.21/troubleshoot-overview.html) _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](http://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 1. ```auto make release build ``` 2. install and launch app 3. ```auto Open VSCode ``` 4. ```auto 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] ``` 5. kpi visualizer does not start ## 3. Observed Behavior kpi visualizer does not start ```auto kpi-visualizer started. Command: kpi-visualizer --kpi=ui-fluidity --output-dir=/Users/tabuchinobuyuki/IdeaProjects/hulu-kepler/generated --grpc-port=50051 --app-name=jp.happyon.android.main --device-serial-number=GT533M06507715E2 --record-cpu-profiling --sourcemap-file-path=/Users/tabuchinobuyuki/IdeaProjects/hulu-kepler/build/debugging/Release/srcmap/b6debc724b9c60c270956dc5bc6f293f6307d6a2e08078c4d5a3b669b09f3272.bundle.map --iterations=3 Running Command: Application UI fluidity Test kpi-visualizer: Data successfully appended to file kpi-visualizer: Perf CLI Version: 0.22.0 kpi-visualizer: Device: Callie Firmware: callie-user OS 1.1 (TV Ship day60/91) kpi-visualizer: Using filtered Perfetto config, disabling CPU scheduling events (ftrace) kpi-visualizer: Installed KSPTService successfully kpi-visualizer: Waiting for trace daemons kpi-visualizer: Waiting 1/10... kpi-visualizer: Waiting 2/10... kpi-visualizer: Waiting 3/10... kpi-visualizer: Waiting 4/10... kpi-visualizer: Waiting 5/10... kpi-visualizer: Waiting 6/10... kpi-visualizer: Waiting 7/10... kpi-visualizer: Waiting 8/10... kpi-visualizer: Waiting 9/10... kpi-visualizer: Waiting 10/10... kpi-visualizer: Error: Appium Kepler Driver is not found in the platform. Please follow instruction in https://developer.amazon.com/docs/kepler/appium-install.html#install-appium to install Appium Kepler Driver. kpi-visualizer exited kpi-visualizer closed ``` ## 4. Expected Behavior _kpi visualizer start_ ### 4.a Possible Root Cause & Temporary Workaround check appium path ```auto % which appium /Users/tabuchinobuyuki/.nodenv/shims/appium % vega exec appium --version dbug Appium Parsed manifest file at /Users/tabuchinobuyuki/.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": "/Users/tabuchinobuyuki/.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 ```auto % appium --version dbug Appium Parsed manifest file at /Users/tabuchinobuyuki/.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": "/Users/tabuchinobuyuki/.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 ```auto % vega exec perf doctor --app-name=jp.happyon.android Spawning /Users/tabuchinobuyuki/vega/sdk/vega-sdk/main/0.22.5875/state/kepler-telemetry/telemetry with args: ['-baseDir', '/Users/tabuchinobuyuki/vega/sdk/vega-sdk/main/0.22.5875/state/kepler-telemetry', '-sendLogsToFile'] Telemetry service started with PID: 29214 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: 11.99 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... √ Max User CPU usage at 81.20% √ Max System CPU usage at 31.60% √ Average User CPU usage at 17.28% √ Average System CPU usage at 9.20% √ Min memory available at 65.22% √ Average memory available at 66.17% ! Device: Not ready for performance testing. Please review lines with X (error) and ! (warnings) symbols. ``` check adb path ```auto % adb --help Android Debug Bridge version 1.0.41 Version 36.0.2-14143358 Installed as /opt/homebrew/bin/adb Running on Darwin 25.3.0 (arm64) ``` ## 5. Logs or crash report _**`(Please make sure to provide relevant logs as attachment)`**_ - i don’t find ExtensionLogs ## 6. Environment _Please fill out the fields related to your bug below:_ - **SDK Version:** `Active SDK Version: 0.22.5875Vega CLI Version: 1.2.18` (also 0.22.5600, 0.22.6006 not working) - **App State:** `[Foreground]` - **OS Information:** Please ssh into the device via `vega exec vda shell` (or `kepler exec vda shell` for v0.21 and earlier) and copy the output from `cat /etc/os-release` into the answer section below. Note, if you don’t have a simulator running or device attached, the command will respond with _`vda: no devices/emulators found`_ * * * ## 👉 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._ ```auto It works on an Intel-based Mac, but it did not work on an Apple silicon (M1/M2/M3) Mac. ``` ---
**Author:** ![Ivy](https://dhm3gbtzu79o6.cloudfront.net/user_avatar/community.amazondeveloper.com/ivy/32/5637_2.png) [@Ivy](https://community.amazondeveloper.com/u/Ivy)\ **Post date:** [February 17, 2026, 12:11pm UTC](https://community.amazondeveloper.com/t/kpi-visualizer-does-not-working/27696/3 "2026-02-17T12:11:43Z")
Hello @nobuyuki.tabuchi I’m looking into this issue and will circle back to you for more information or with updates. Warm regards, Ivy ---
**Author:** ![Ivy](https://dhm3gbtzu79o6.cloudfront.net/user_avatar/community.amazondeveloper.com/ivy/32/5637_2.png) [@Ivy](https://community.amazondeveloper.com/u/Ivy)\ **Post date:** [February 19, 2026, 6:21am UTC](https://community.amazondeveloper.com/t/kpi-visualizer-does-not-working/27696/4 "2026-02-19T06:21:25Z")
Hi @nobuyuki.tabuchi , The KPI Visualizer error is coming from here: ```auto if not _KEPLER_DRIVER_INSTALL_PATTERN.findall( re.sub(_KEPLER_DRIVER_LIST_STDOUT_ANSI_CODE, "", drivers_installed.stderr)): raise FatalError( f"Appium Kepler Driver is not found in the platform. Please follow instruction " f"in {DOC_KEPLER_APPIUM_URL} to " f"install Appium Kepler Driver.") ``` Looking at 4.a. that you have shared above: ```auto % which appium /Users/tabuchinobuyuki/.nodenv/shims/appium ``` The command that is executed by KPI Visualizer that is failing is: ` driver list` Can you please run `which appium` and then use the output of that and add `driver list` ? Example using my machine: ```auto shenoy@bcd07445a6be ~ % which appium /Users/shenoy/.nvm/versions/node/v22.22.0/bin/appium # Note: Use full path of `which appium` shenoy@bcd07445a6be ~ % /Users/shenoy/.nvm/versions/node/v22.22.0/bin/appium driver list dbug Appium Parsed manifest file at /Users/shenoy/.appium/node_modules/.cache/appium/extensions.yaml: { dbug Appium "drivers": { dbug Appium "kepler": { dbug Appium "pkgName": "@amzn/appium-kepler-driver", dbug Appium "version": "3.31.0", dbug Appium "installType": "local", dbug Appium "installSpec": "/Users/shenoy/.kepler_appium/AKDInstallation/src/AppiumKeplerDriver", dbug Appium "installPath": "/Users/shenoy/.kepler_appium/AKDInstallation/src/AppiumKeplerDriver", 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 } ✔ Listing available drivers - kepler@3.31.0 [installed (linked from /Users/shenoy/.kepler_appium/AKDInstallation/src/AppiumKeplerDriver)] - uiautomator2 [not installed] - xcuitest [not installed] - mac2 [not installed] - espresso [not installed] - safari [not installed] - gecko [not installed] - chromium [not installed] ``` You should also use the full path of appium in the command as shown below, since you have run `appium --version`. ```auto which appium --version version ``` Example ```auto shenoy@bcd07445a6be ~ % /Users/shenoy/.nvm/versions/node/v22.22.0/bin/appium --version dbug Appium Parsed manifest file at /Users/shenoy/.appium/node_modules/.cache/appium/extensions.yaml: { dbug Appium "drivers": { dbug Appium "kepler": { dbug Appium "pkgName": "@amzn/appium-kepler-driver", dbug Appium "version": "3.31.0", dbug Appium "installType": "local", dbug Appium "installSpec": "/Users/shenoy/.kepler_appium/AKDInstallation/src/AppiumKeplerDriver", dbug Appium "installPath": "/Users/shenoy/.kepler_appium/AKDInstallation/src/AppiumKeplerDriver", 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 ``` Warm regards, Ivy ---
**Author:** ![nobuyuki.tabuchi](https://dhm3gbtzu79o6.cloudfront.net/user_avatar/community.amazondeveloper.com/nobuyuki.tabuchi/32/1916_2.png) [@nobuyuki.tabuchi](https://community.amazondeveloper.com/u/nobuyuki.tabuchi)\ **Post date:** [February 24, 2026, 1:22am UTC](https://community.amazondeveloper.com/t/kpi-visualizer-does-not-working/27696/5 "2026-02-24T01:22:35Z")
Hi, @Ivy I ran the command. Could you take a look and confirm? ```auto % which appium /Users/tabuchinobuyuki/.nodenv/shims/appium ``` ```auto % /Users/tabuchinobuyuki/.nodenv/shims/appium driver list dbug Appium Parsed manifest file at /Users/tabuchinobuyuki/.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": "/Users/tabuchinobuyuki/.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 } ✔ Listing available drivers - kepler@3.30.0 [installed (npm)] - uiautomator2 [not installed] - xcuitest [not installed] - mac2 [not installed] - espresso [not installed] - safari [not installed] - gecko [not installed] - chromium [not installed] ``` Kind regards, Nobuyuki ---
**Author:** ![Ivy](https://dhm3gbtzu79o6.cloudfront.net/user_avatar/community.amazondeveloper.com/ivy/32/5637_2.png) [@Ivy](https://community.amazondeveloper.com/u/Ivy)\ **Post date:** [February 24, 2026, 6:58am UTC](https://community.amazondeveloper.com/t/kpi-visualizer-does-not-working/27696/6 "2026-02-24T06:58:07Z")
Sure @nobuyuki.tabuchi , taking a look. ---
**Author:** ![Ivy](https://dhm3gbtzu79o6.cloudfront.net/user_avatar/community.amazondeveloper.com/ivy/32/5637_2.png) [@Ivy](https://community.amazondeveloper.com/u/Ivy)\ **Post date:** [February 25, 2026, 5:31am UTC](https://community.amazondeveloper.com/t/kpi-visualizer-does-not-working/27696/7 "2026-02-25T05:31:09Z")
Hi @nobuyuki.tabuchi From what I can tell, the `nodeenv` installation could be causing issues. The instructions for installing Node.js are [here](https://developer.amazon.com/docs/vega/0.22/install-vega-sdk.html). “Node.js: Download and install Node.js (version 18.x or later)” from [this link](https://nodejs.org/en/download). So, the you should probably switch to nvm. Here’s a short python script (attached) to diagnose. You can run this before switching to nvm so we can get the results with nodeenv. To run, **python3 diagnose\_appium.py** Here is diagnose\_appium.py ```auto #!/usr/bin/env python """Appium driver detection diagnostic""" from subprocess import run import re # Get appium path and run driver list appium_path = run(["which", "appium"], encoding="utf-8", capture_output=True).stdout.strip() result = run([appium_path, "driver", "list"], encoding="utf-8", capture_output=True) print(f"Appium path: {appium_path}\n") # Show raw outputs print("="*60) print(f"STDOUT ({len(result.stdout)} chars):") print("="*60) print(result.stdout if result.stdout else "(empty)") print("\n" + "="*60) print(f"STDERR ({len(result.stderr)} chars):") print("="*60) print(result.stderr[:800] if result.stderr else "(empty)") # Limit to 800 chars # Pattern matching ANSI = r"\x1b\[[0-9;]*m" PATTERN = r"kepler@\d+\.\d+\.\d+ \[installed .*?\]" stdout_cleaned = re.sub(ANSI, "", result.stdout) stderr_cleaned = re.sub(ANSI, "", result.stderr) stdout_match = re.findall(PATTERN, stdout_cleaned) stderr_match = re.findall(PATTERN, stderr_cleaned) # Results print("\n" + "="*60) print("RESULTS:") print("="*60) print(f"Driver in STDOUT: {'Yes' if stdout_match else 'No'}") print(f"Driver in STDERR: {'Yes' if stderr_match else 'No'}") print(f"Test: {'PASS' if (stdout_match or stderr_match) else 'FAIL'}") if stdout_match or stderr_match: print(f"Found: {(stdout_match or stderr_match)[0]}") ``` Example: ```auto python3 diagnose_appium.py Appium path: /Users/shenoy/.nvm/versions/node/v22.22.0/bin/appium ============================================================ STDOUT (0 chars): ============================================================ STDERR (1291 chars): ============================================================ dbug Appium Parsed manifest file at /Users/shenoy/.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": "/Users/shenoy/.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":============================================================ RESULTS: ============================================================ Driver in STDOUT: No Driver in STDERR: Yes Test: PASS Found: kepler@3.30.0 [installed (npm)] ``` Warm regards, Ivy ---
**Author:** ![system](https://dhm3gbtzu79o6.cloudfront.net/user_avatar/community.amazondeveloper.com/system/32/5065_2.png) [@system](https://community.amazondeveloper.com/u/system)\ **Post date:** [March 17, 2026, 6:01am UTC](https://community.amazondeveloper.com/t/kpi-visualizer-does-not-working/27696/8 "2026-03-17T06:01:38Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed. ---
**Author:** ![Ivy](https://dhm3gbtzu79o6.cloudfront.net/user_avatar/community.amazondeveloper.com/ivy/32/5637_2.png) [@Ivy](https://community.amazondeveloper.com/u/Ivy)\ **Post date:** [March 17, 2026, 6:02am UTC](https://community.amazondeveloper.com/t/kpi-visualizer-does-not-working/27696/9 "2026-03-17T06:02:05Z")
Hey @nobuyuki.tabuchi I hope the updates shared have helped you. Closing this topic as there’s no interaction. If you still face this issue, please feel free to reach out to us. Happy to help! Warm regards, Ivy