Skip to content

VS Code Tizen Extension: Update 10.3.1 persistently breaks an existing web app build #74

@stan423321

Description

@stan423321

I'm running VS Code with Tizen Extension on Ubuntu Linux 24.04.4 LTS.

After last night's (?) update of VS Code Tizen Extension to version 10.3.1, an internal project that has been built successfully two days ago with tooling managed by version 10.3.0 cannot be built anymore.

The following error pop-ups are shown after an attempt to build:
"Build failed. Please check the Output window for more details."
"Tizen SDK Not Found: Please ensure Tizen SDK is properly installed and the SDK path is configured correctly."

Sample output tab output:

2026-04-30 14:11:14.176 [info] [SVR] [SDKPathManager] SDK Extract path: /home/s.dobrowolsk/.tizen-extension-platform/server/sdktools/data
2026-04-30 14:11:14.177 [info] [SVR] [SDKPathManager] Tools path (before mkdir check): /home/s.dobrowolsk/.tizen-extension-platform/server/sdktools/data/tools
2026-04-30 14:11:14.177 [info] [SVR] [SDKPathManager] Final tools path: /home/s.dobrowolsk/.tizen-extension-platform/server/sdktools/data/tools
2026-04-30 14:11:14.177 [info] [SVR] [SDKPathManager] Tools path: /home/s.dobrowolsk/.tizen-extension-platform/server/sdktools/data/tools
2026-04-30 14:11:14.177 [info] [SVR] [SDKPathManager] Calculated tz path: /home/s.dobrowolsk/.tizen-extension-platform/server/sdktools/data/tools/tizen-core/tz
2026-04-30 14:11:14.177 [info] [SVR] [SDKPathManager] tz.exe exists: false
2026-04-30 14:11:14.177 [info] [SVR] [SDKPathManager] tz.exe not found, returning null
2026-04-30 14:11:14.178 [error] [EXT] API Error - Status: 400 | {"url":"/api/v1/project/build","data":{"status":"error","errorCode":"BUILD_FAILED","message":"tz path is undefined"}}

2026-04-30 14:11:14.178 [info] [EXT] tz path is undefined

I don't know if specific mention of tz.exe is of interest, given the intertwined ecosystems involved. Directory /home/s.dobrowolsk/.tizen-extension-platform/server/sdktools/data/tools/ exists; tizen-core within it does not.

Reverting the extension to version 10.3.0 doesn't help; it only adds an additional pop-up about "extension server" expecting version 10.3.1. Speculation: presumably, the core part of extension v. 10.3.1 updated the extension server and v. 10.3.0 doesn't undo it, and the error is at least partially caused by the server?

After re-updating to 10.3.1, I tried installing all the packages available within the extension's package menu. The messages didn't change.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions