Languages

Menu
Sites
Language
Problem creating valid certificate

While the steps how to create and register own certificate are well documented, I fail to create a new certificate that is accepted by the device/emulator. It has been seen earlier that there are many things that can go wrong (see notes), and obviously I'm missing something in here.

Notes:

  • If certificate is created with JDK 1.6, the certificate is considered invalid
  • If device/emulator clock is in the past, the certificate is considered invalid
  • I've created certificate both with CLI and IDE, but package created with
  • I do have a valid certificate that works (so the issue is not in packaging process), but now I wanted to sign package with different p12 certificate

Questions:

  • If device is running Tizen 2.2.0, can SDK 2.2.1 be used for creating package (however, installing SDK 2.2.1 signed package cannot be installed in 2.2.1 emulator)? How about SDK 2.2.1 vs. Tizen 2.1? 
  • What are other things that might affect on package signing?
  • What is the algorithm for hashing the password in profiles.xml? Currently I'm copying the relevant parts from IDE generated profiles.xml into version control.

References / similar issues:

  • https://developer.tizen.org/forums/sdk-ide/web-application-signing-cli
  • https://developer.tizen.org/forums/sdk-ide/cli-certified-package-considered-invalid-33
List

Responses

4 Replies
Marco Buettner

Q1: You can creating package if Tizen SDK 2.2.1 for Tizen 2.2.0, but APIs which available only since 2.2.1 are not able to use! But It should no new API available for 2.2.1. Also you can use Tizen SDK 2.2.1 for Tizen 1.0, Tizen 2.1 and so on... But its recommend to create 2.2 files, because it will not device will be available with before Tizen 2.2 ;)

Q2; Valid config.xml

Q3: Why you edit profiles.xml?

Juha Mustonen

Thanks for your response.

Q2: I suppose it is possible, but since the same config.xml works with existing p12 certificate, it should not be an issue here?

Q3: Because of absolute paths to certificates: Application packaging is part of the build process which can be executed in different environments. Therefore, also tizen-developer-ca.cer and tizen-distributor-ca.cer are included in repository and being referenced from there.

Juha Mustonen

Oh, I think I just found the rootcause: Application installed with old certificate needs to be uninstalled before installing new one - otherwise you'll get the INVALID_CERTIFICATE error.

Once again something that should be documented, IMHO.

AVSukhov

Hello,

Thanks for sharing information. It may be useful.