Languages

Menu
Sites
Language
Build/Package from Command Line?

Has anyone been able to do this successfully? I've tried to do this using the instructions on the Command Line Interface page here: https://wiki.tizen.org/wiki/SDK/How_To_Use_Tizen_SDK_CLI_Tools

It looks like I'm able to use all of the commands, and they don't appear to report any failures, but when I go to deploy the app to the device using web-install it fails with this error:

'hellobear.wgt' file transfer successful.
'1To83yLZsR.hellobear' install failed.
Check author certificates in Preferences > Tizen SDK > Secure Profiles > Profile items.
CrazyDiamond:.
 
I've seen an issue where the date on the device doesn't match, but I've fixed the date on the device and that still hasn't solved the problem. Does anyone have any advice?
 
Thanks
Edited by: Brock Boland on 17 Mar, 2014 Reason: Paragraph tags added automatically from tizen_format_fix module.
List

Responses

8 Replies
konduri sai swathi
Hi, What is the SDK version you are using ? If it's 2.2 then author certificate will be created in /home/username/tizen-sdk-data/keystore/author/ directory when you generate the certificate with the steps mentioned in the link, so specify this path in profiles.xml file.
Patrick Casao
I'm using 2.2, and the path to the author certificate (pcasao3.p12) is already specified in the profiles.xml file, at the exact location you've indicated.
konduri sai swathi
Hi, Share your profiles.xml file. 
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<profiles version="2.2">
<profile name="test">
<profileitem ca="/home/nitish/tizen-sdk/tools/certificate-generator/certificates/developer/tizen-developer-ca.cer" distributor="0" key="/home/nitish/tizen-sdk-data/keystore/author/tizen567.p12" password="tizen567" rootca=""/>
<profileitem ca="/home/nitish/tizen-sdk/tools/certificate-generator/certificates/developer/tizen-developer-ca.cer" distributor="1" key="/home/nitish/tizen-sdk-data/keystore/author/tizen567.p12" password="tizen567" rootca=""/>
</profile>
</profiles>
Above is the profiles.xml file i edited. Also change the password to the password you have given while generating the certificate. Copy Paste above code in your xml file and replace the "key" with the path of your certificate and try.
Patrick Casao
Here's my profiles.xml. I created a brand new certificate to test this, but I still get a warning to check the secure profiles.
Patrick Casao
Can't seem to post the profiles.xml data, every time I try it just gives me a blank code section. Here it is at pastebin: http://pastebin.com/Lj3yi0B2
marc derosa
Just FYI Patrick. I'm seeing the same error message here when I build through the command line tools. It seems very unlikely that the cause has anything to do with the profile.xml (and associated files listed inside) as I can build and deploy using that same profile.xml from within the IDE. Otherwise a quick check of the *.wgt file built by the command line tools has all signature files that I am expecting and those file formats looks Ok as well.
marc derosa
Hi Patrick, To get this working I had to remove the .project file in my .buildResult directory. The console tools ask for that file but don't give it to them. Instead to get the build automated add the -n option to prevent the command line tools from putting the build in a wait state. Something like: web-build ./ cd .buildResult web-signing -n -profile production:/path/to/your/profiles.xml web-packaging -n bestparking.wgt For the people in change of the console build tools. You should not be asking for a .project file. These file are generally not part of source control so if we are doing a build on a build machine this file will not be handy., We also may very well not be using Eclipse to develop. Don't assume. Beyond that if your tools ask for a .project file they should at least be able to handle the existence of one without causing the deployment process to break later on.
Bucky

"To get this working I had to remove the .project file in my .buildResult directory."

Thank you Marc! I had the exact same error as Patrick, and it was driving me crazy, because I had gotten signing to work previously so I know my certificates were correct. The root cause was that I had created a zero byte ".project" file to skip the prompts, and apparently that messed up the signing. Once I removed the .project file, it worked again.