语言

Menu
Sites
Language
Visual Studio Code package Build Error

Hi,

I am trying to build an image with "Tizen TV:build package" in Visual Studio Code in macOS.

I changed Settings.json file below

"tizen.profiles.path": "/Users/MSeo1/tizen-studio-data/profile/profiles.xml",

But still getting the error below, guessing the error is caused by failing in reading profiles.xml file as below.

Is there any reason it keeps reading the Active profile name as tizentvapp rather than an actual name in Certificate?

1:21:54 AM##_P12ToPem: Active profile name:tizentvapp
1:21:54 AM##_P12ToPem: Find active profile:tizentvapp

 

The whole build log.

1:21:54 AM##_SDB Command Prompt: setCommand:export PATH=/Users/MSeo1/.vscode/extensions/tizensdk.tizentv-1.0.2/tools/sdb/mac:$PATH
1:21:54 AM##_Build Package: ==============================Build Package start!
1:21:54 AM##_Build Package: If is debug mode ,set workspace to current work dir
1:21:54 AM##_Build Package: The app's path is: /Users/MSeo1/project/vscode_tizen
1:21:54 AM##_Build Package: The app's name is: vscode_tizen
1:21:54 AM##_<WARNING>_## Build Package: The existing /Users/MSeo1/.vscode/extensions/tizensdk.tizentv-1.0.2/resource/certificate-generator/certificates/developer/active_cert/tizen_developer_private_key.pem will be removed firstly
1:21:54 AM##_Build Package: Remove existing /Users/MSeo1/.vscode/extensions/tizensdk.tizentv-1.0.2/resource/certificate-generator/certificates/developer/active_cert/tizen_developer_private_key.pem
1:21:54 AM##_<WARNING>_## Build Package: The existing /Users/MSeo1/.vscode/extensions/tizensdk.tizentv-1.0.2/resource/certificate-generator/certificates/developer/active_cert/tizen_developer_cert.pem will be removed firstly
1:21:54 AM##_Build Package: Remove existing /Users/MSeo1/.vscode/extensions/tizensdk.tizentv-1.0.2/resource/certificate-generator/certificates/developer/active_cert/tizen_developer_cert.pem
1:21:54 AM##_<WARNING>_## Build Package: The existing /Users/MSeo1/.vscode/extensions/tizensdk.tizentv-1.0.2/resource/certificate-generator/certificates/distributor/active_cert/tizen_distributor_private_key.pem will be removed firstly
1:21:54 AM##_Build Package: Remove existing /Users/MSeo1/.vscode/extensions/tizensdk.tizentv-1.0.2/resource/certificate-generator/certificates/distributor/active_cert/tizen_distributor_private_key.pem
1:21:54 AM##_<WARNING>_## Build Package: The existing /Users/MSeo1/.vscode/extensions/tizensdk.tizentv-1.0.2/resource/certificate-generator/certificates/distributor/active_cert/tizen_distributor_cert.pem will be removed firstly
1:21:54 AM##_Build Package: Remove existing /Users/MSeo1/.vscode/extensions/tizensdk.tizentv-1.0.2/resource/certificate-generator/certificates/distributor/active_cert/tizen_distributor_cert.pem
1:21:54 AM##_Build Package: Signing app, please wait...
1:21:54 AM##_signPackage: ==============================Signature Package start!
1:21:54 AM##_signPackage: If it is debug mode, set workspace to current directory
1:21:54 AM##_P12ToPem: ================Check Active Profile
1:21:54 AM##_P12ToPem: ================Load Profile
1:21:54 AM##_P12ToPem: Profile file path:/Users/MSeo1/.vscode/extensions/tizensdk.tizentv-1.0.2/resource/profiles.xml
1:21:54 AM##_P12ToPem: Active profile name:tizentvapp
1:21:54 AM##_P12ToPem: Find active profile:tizentvapp
1:21:54 AM##_P12ToPem: Developer p12 File: /Users/MSeo1/.vscode/extensions/tizensdk.tizentv-1.0.2/resource/Author/tizentvapp.p12
1:21:54 AM##_P12ToPem: Distributor p12 File: /Users/MSeo1/.vscode/extensions/tizensdk.tizentv-1.0.2/resource/certificate-generator/certificates/distributor/tizen-distributor-signer.p12
1:21:54 AM##_P12ToPem: authorPassword:OOOOO
1:21:54 AM##_P12ToPem: distributorPassword:OOOOO
1:21:54 AM##_<WARNING>_## Build Package: Do application signature failed, please check your environment
1:21:54 AM##_<WARNING>_## Build Package: xmldom is suggested for signature package
1:21:54 AM##_Build Package: NaN
1:21:54 AM##_<ERROR>_## Build Package: Failed to build package!

响应

1 回复
Tizen .NET

Sorry for the late response.
According to the person in charge, the latest extension version 1.0.3 has been released to vscode market on April 24th and it is said that it works fine with it on Mac.
Please check it again with this update.
We hope that your problem has been resolved.
Thanks.