Languages

Menu
Sites
Language
Certificates issue

Hello guys,

I'm trying to install a test application on my new Gear S2 and it doesn't work.
I tried to install both Native and Web applications.
Errors are a bit different.
Below is the example of a Web-based image installations. (Error: SIGNATURE_INVALID [22] failed)

I work on OSX 10.11.4. 
Tizen SDK version 2.4.0_Rev5 ; Build id : 20151223-1448

I did go through Certificate installation and I have them in /Volumes/HDD/Users/iGeophysix/tizen-sdk-data/keystore/Profile1 folder
I tried to uninstall the SDK and did full restart on my watches. What else can I try?
 

Regards,
Alexander Filimonov

 

Launching the Tizen application...

# If you want to see the detailed information,

# please set the logging level to DEBUG in Preferences and check the log file in '/Volumes/HDD/Users/iGeophysix/tizen-sdk-data/ide/logs/ide-20160415_000633.log'.

 

[Initializing the launch environment...]

    RDS: On

    Target information: SM-R732

    Application information: Id(M6iOD8yCxr.DigitalWatch1), Package Name(M6iOD8yCxr), Project Name(DigitalWatch1)

[Transferring the package...]

    Transferred the package: wgt stream -> /opt/usr/apps/tmp/DigitalWatch1.wgt

[Installing the package...]

path is /opt/usr/apps/tmp/DigitalWatch1.wgt

start process (install)

....

error : 22

 

end process (fail)

processing result : SIGNATURE_INVALID [22] failed

spend time for pkgcmd is [31812]ms

cmd_ret:22

[Transferring the package...]

    Transferred the package: wgt stream -> /opt/usr/apps/tmp/DigitalWatch1.wgt

path is /opt/usr/apps/tmp/DigitalWatch1.wgt

start process (install)

....

error : 22

 

end process (fail)

processing result : SIGNATURE_INVALID [22] failed

spend time for pkgcmd is [49960]ms

cmd_ret:22

Unexpected stop progress...

(112.439 sec)

List

Responses

10 Replies
Alexander Filimonov

By the way... I also noticed that certificate is being sent with tomorrow's date on the device (e.g., if today is 15th of April, the device-profile.xml file would be of April 16th!)

daniel kim

Hi,

Have you performed "permit to install applicaiton" button on connection explorer?

   http://developer.samsung.com/gear/develop/getting-certificates/permit-device

Regards

Alexander Filimonov

Hi,

I did. And that is where I found this interesting fact, that the device-profile.xml file has date of modification of the next day.

 

Masum Talukder

Hello,

I would suggest you to check this post: https://developer.tizen.org/forums/sdk-ide/signature-invalid?langredirect=1

Alexander Filimonov

Nope. Doesn't help either.

I don't have certificate-registration.xml at all.

Masum Talukder

Hello,
SIGNATURE_INVALID [22] usually means the certificate that you created to start the process doesn't match the device profile that was downloaded. There are 3 parts to the Tizen Wearable signing process

1. Your certificate that you create using the Tizen IDE. This file is in ~/tizen-wearable-sdk-data/keystore/author.csr.

2. Your certificate that has been co-signed using the Samsung Developer account and returned to you in email in a file named author.crt

3. A device profile that is unique to the device you are debugging. This is created by the Samsung Developer site based on information you provide. The result is sent in an email as device_profile.xml. You sign this profile with your author certificate and install. If the signature used to sign this profile doesn't match the original author.csr, then it will fail.


I think you should re-generate the 'author certificate' and 'Device Profile' using your current device DUID and click the 'permit to install application' in connection explorer.

and if the problem presists then check the following:

1. Delete [~/workspace/.metadata ] folder

2. Open the device-profile.xml in editor and check the <TestDevice> DUID </TestDevice> contains the correct DUID of your device in this tag.

 

If you think that my answer is helpful for you, then please mark it as the "Best" answer.

Alexander Filimonov

What I found is that in my device_profile.xml file certificate is absolutely different to what is written in author.csr.

And after some looking around I found that it is similar to what is written in ~/tizen-sdk/tools/certificate-generator/certificates/developer/tizen-developer-ca-privatekey.pem

It seems that the interface I use to make certificates does something wrong.

Alexander Filimonov

By the way, I\m currently running Tizen SDK
Version : 2.4.0_Rev5
Build id : 20151223-1450
OS: Ubuntu (and also tied on OSX El Capitan) on different computers. Both are new installs.

Masum Talukder

Hello Alexander Filimonov.

Have you followed my earlier post instructions?

Alexander Filimonov

Hi Masum,

I did. At least I tried to.
How about remote session? I'm using TeamViewer.