Vega Studio is not detecting the physical and virtual device in the current latest version(v0.22.4)

Vega Open Beta Bug Reports
1

Hi Vega Team!

This is a report and sharing of a problem I found regarding VegaStudio.

:white_square_button:Problem
Neither the physical device nor the KVD are being detected.

:white_square_button:Background
Just a few days ago, both the physical device and the KVD worked perfectly in the exact same environment,
but suddenly the problem of the physical and virtual device not being detected occurred. I was quite puzzled.

:white_square_button:Temporary Solution
Revert VegaStudio to the previous version v0.22.3.
Since VegaStudio’s Auto Update is enabled in VSCode, it’s likely that it was updated to the latest version without my knowledge, which is probably why this problem suddenly occurred.

I think it’s best to address this problem as soon as possible after upgrading VegaStudio from v0.22.3 to v0.22.4.

Warm regards,
soseh

3

Hello @soseh

Thank you for reporting this issue and for the detailed investigation - identifying that the regression started with the Vega Studio v0.22.4 auto-update is very helpful.

We are looking into this and will investigate the device detection changes between v0.22.3 and v0.22.4. In the meantime, could you please provide the following to help us reproduce and debug:

  1. OS - Are you on macOS (Intel or Apple Silicon) or Ubuntu?
  2. Vega CLI version - Output of vega --version
  3. SDK version - Output of vega sdk version (or check in Vega Studio)
  4. Physical device model - Fire TV Stick 4K Select?
  5. Connection method - USB or TCP/IP?
  6. Error output - What does vega device list return when the issue occurs? (any error message or just empty?)
  7. VVD behavior - Does vega virtual-device start from the terminal also fail, or is it only Vega Studio’s UI that doesn’t detect it?

Workaround: Reverting Vega Studio to v0.22.3 resolves the issue. To prevent auto-updates in the meantime, you can disable auto-update for the extension in VS Code:

  • Extensions → Vega Studio → gear icon → Disable Auto Update

We will update you once we have more information on the v0.22.4 regression.

Warm regards,
Ivy

4

Hi @Ivy_Mahajan

identifying that the regression started with the Vega Studio v0.22.4 auto-update is very helpful.

We can almost certainly conclude that.
the issue starting from version v0.22.4.

OS - Are you on macOS (Intel or Apple Silicon) or Ubuntu?

Please refer to the image below.

スクリーンショット 2026-05-11 18.04.25
スクリーンショット 2026-05-11 18.04.25936×986 50.6 KB

Vega CLI version - Output of vega --version

SDK version - Output of vega sdk version (or check in Vega Studio)

The version I’m currently using is v0.22.6759, but I’ve also checked v0.22.6150 and v0.22.6620, and the same problem exists.

スクリーンショット 2026-05-11 18.18.29
スクリーンショット 2026-05-11 18.18.29794×122 8.36 KB

Physical device model - Fire TV Stick 4K Select?

YES

Connection method - USB or TCP/IP?

USB

Error output - What does vega device list return when the issue occurs? (any error message or just empty?)

Vega device has been detected.
but it doesn’t show up in DEVICES section.

スクリーンショット 2026-05-11 17.58.41
スクリーンショット 2026-05-11 17.58.41822×110 7.6 KB

VVD behavior - Does vega virtual-device start from the terminal also fail, or is it only Vega Studio’s UI that doesn’t detect it?

It’s similar to number 6.
KVD starts up, but it doesn’t show up in DEVICES section.

One point to add:
Everything is working correctly with the commands,
for example application can be correctly installed too
by the command “vega device install-app --packagePath xx.vpkg”.

The current problem is that the physical device and KVD can not showing up in VegaStudio DEVICES section.

スクリーンショット 2026-05-11 18.27.31
スクリーンショット 2026-05-11 18.27.31654×258 6.49 KB

and then to run app, The following error dialog box appears.

スクリーンショット 2026-05-11 18.27.55
スクリーンショット 2026-05-11 18.27.551010×366 41.9 KB

Warm regards,
soseh

5

Hi @soseh, Thanks for reporting can you please use this button and share us log that got generated.

image
image2126×1862 166 KB

or you can open extension log’s folder and attach the logs please.

image
image1380×158 16.6 KB

6

Hi @Ivy_Mahajan,
we are also facing the same issue today.
The physical device is not showing under the Vega devices list. but we are able to see the devices list in terminal for the command “vega exec vda devices”

Active SDK Version: 0.22.6150
Vega CLI Version: 1.2.18

Warm regards,
Yupp TV.

7

Hi @YuppTV and @soseh

We are actively investigating the issue, would you please provide the os information with the instruction below:

It would also be helpful to provide the extension log with the instruction posted by @Suresh above. Thank you!

OS Information
Please ssh into the device via kepler exec vda shelland copy the output from cat /etc/os-releaseinto the answer section below. Note, if you don’t have a simulator running or device attached kepler exec vda shell will respond with vda: no devices/emulators found

  • NAME="OS"
OE_VERSION="4.0.0"
OS_MAJOR_VERSION="1"
OS_MINOR_VERSION="1"
RELEASE_ID="2"
OS_VERSION="1.1"
BRANCH_CODE="VegaMainlineTvIntegration"
BUILD_DESC="OS 1.1 (VegaMainlineTvIntegration/4418)"
BUILD_FINGERPRINT="4.0.155683.0(3072cab629675a74)/4418N:user-external/release-keys"
BUILD_VARIANT="user-external"
BUILD_TAGS="release-keys"
BUILD_DATE="Wed Sep 03 05:40:19 UTC 2025"
BUILD_TIMESTAMP="1756878019"
VERSION_NUMBER="201010441850"
8

hi @Suresh

Thanks for reporting can you please use this button and share us log that got generated.

.gz file can not be uploaded.

or you can open extension log’s folder and attach the logs please.

I’ve attached the NG log after starting KVD in VegaStudio v0.22.4. Please check it.

CoreModule-2026-05-12.log (30.6 KB)

Vega.log (237 Bytes)

vega-studio-2026-05-12.log (90.9 KB)

Just in case
I also attached the OK log after starting KVD in VegaStudio v0.22.3.

CoreModule-2026-05-12.log (117.8 KB)

Vega.log (237 Bytes)

vega-studio-2026-05-12.log (104.1 KB)

Warm regards,
soseh

9

hi @yanbiden

I’ve attached OS information after starting KVD in VegaStudio v0.22.4.
Please check it.

kvd-tv:/$ 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/10675730)”
BUILD_FINGERPRINT=“1.0.67573.0(9a1d8dfa7da5d600)/10675730N:user/dev-keys”
BUILD_VARIANT=“user”
BUILD_TAGS=“dev-keys”
BUILD_DATE=“Fri Feb 13 11:51:33 UTC 2026”
BUILD_TIMESTAMP=“1770983493”
VERSION_NUMBER=“1402077573030”

Just in case
I also attached OS information after starting KVD in VegaStudio v0.22.3.

kvd-tv:/$ 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/10675730)”
BUILD_FINGERPRINT=“1.0.67573.0(9a1d8dfa7da5d600)/10675730N:user/dev-keys”
BUILD_VARIANT=“user”
BUILD_TAGS=“dev-keys”
BUILD_DATE=“Fri Feb 13 11:51:33 UTC 2026”
BUILD_TIMESTAMP=“1770983493”
VERSION_NUMBER=“1402077573030”

Warm regards,
soseh

10

@soseh thank you.
This is being looked at with Priority.

Warm Regards,
Ivy

11

@YuppTV would it be possible for you to create another topic here so that we can track and cater to you better?
Thanks!

12

sure will create another topic for this @Ivy_Mahajan .

Thanks.

13

Thank you @soseh , this is very helpful. We are able to confirm the root cause. There will be a release this week to fix the issue.

14

Hi @soseh @YuppTV

There is a new version (v0.22.5) released today with the fix of the issue, it’s available from the marketplace.

15

Hi @yanbiden

Thank you for your prompt response.
I’ve checked v0.22.5 here.
It’s OK.