Tizen Forums

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.

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.

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.

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.