언어 설정

Menu
Sites
Language
Certificates is really difficult thing

 

  I want to say that the certificates is really difficult thing. it's
Especially if you have two SDC 2.3. and  for wearable.
  Everyone can feel it on their skin.
  I recently removed the old certificates due to mess and removed SDC for wearable.
 I began to do all in 2.3.  for device wearable. There's a hand made certificate as in the Help of SDC 2.3.
  Application for wearable was rejected registration with reason.

AUTHOR SIGNATURE ERROR. UNKNOWN ERROR
Title : SDK Default key was used
Detailed : SDK default key was used. To publish developer own key should be used with Registration file
For more information, refer to IDE > Help Contents > Generating a certificate request
Or, Help Contents > Getting Started with Tizen wearable > Development Environment > Tizen SDK for wearable > Certificates


  What's wrong here? I  made by myself certificate for all devices. So it is impossible? Then it have  to be writen in  Help  2.3 sdc , I think...

목록

Responses

23 댓글
daniel kim

Hi,

Did you create your certificate from the "Request and Register a Certificate" menu on the IDE?

If yes, I suggest you to check active profiles on below menu.

 Window--> Preferences --> Tizen SDK --> Security Profiles

Hope this will help you.

 

Kilim A

I speak about 2.3 SDC There no any Request and Register a Certificate

 Must i have two sdc?

 One  for register certificate Two - for work
 

Alex Dem

Hi, 
fyi: for SDK 2.3.0rev2 you could install certificate extension (it is requred for Samsung Z1 mobiles) See also here (maybe could help):
https://developer.tizen.org/forums/native-application-development/problems-installing-tpk-on-samsung-z1
Alexey.

pradeep ramaiah

Hi,

Download the certificate extn from http://developer.samsung.com/samsung-z.

and install the certificates using install manger.

Then you can see the request certificate .

Kilim A

But for wearable it was not work, right?

Must i have 2 sdk?

 I think... yes :(
 

Kilim A

2 SDK are interfere with each other. It  is as for certificates.

Support recomended me

"Regarding your inquiry, we would regrettably inform you that we could not provide more technical support in your case.


However, we would suggest you to read the detail page of “Signing Applications in Android” (http://developer.samsung.com/technical-doc/view.do?v=T000000055).


Also, we would suggest you the Samsung Developer if you need more technical support: http://developer.samsung.com/home.do"

 

 I do not know what to do with it.

Kilim A

Could somebode tell me - we must use two certoficates ( one for wearable and one for z telefon) or we can use one for two device?
 

Marco Buettner

I have one certificate for all my tizen applications (wearables, mobile, tv)

AVSukhov

Hello,

You can install SDK 2.3 (modile - web and native, wearable) and certificate extension.

After this when you request device-profile.xml you need add all your devices (DUID) mobile and wearable.

A few tips from me:

1. Before install SDK 2.3 delete previous SDK and all data folders (tizen-sdk and tizen-data-sdk)

2. Install SDK 2.3 (mobile + wearable)

3. Install Certificate extension

4. When launch IDE create new workspace

5. Using guide in IDE -> Help -> Help Contents -> Certificates, request and isntall certificate

Kilim A

 

 Hello

Thank you

 This is useful

Where we can get DUID for all devices?
 

AVSukhov

Hello,

In the Connection Explorer view (IDE), right-click a device

Select Properties 

In opened window select Info

Kilim A

I have not real watch and z fon... only PQ for developers

 so  for wearable i use virtual UID

Kilim A

I have not real watch and z fon... only PQ for developers

 so  for wearable i use virtual UID

Kilim A

Can you tell me what kind of password  is here

 

Is it the same  like password for author string ( above)?

Alex Dem

Hi, 
I am not think that the password is identical with any known password.

Regarding distributor certificates a couple of strings here:
https://developer.tizen.org/dev-guide/2.3.0/org.tizen.gettingstarted/html/dev_env/register_author_certificate.htm

Also there was a topic regarding password for old Tizen 2.2.1 (but not for wearable) https://developer.tizen.org/forums/sdk-ide/how-get-distributor-certificate-password but as I remember I could not use this password for 2.2.1. 
I am not sure that If you enter wrong password for 'first distributor certificate' you will able to restore old right password after.

Alexey.

AVSukhov

Hello,

If you request device-profile.xml and create distributor cert according documentation then password presented in email with device-profile.xm

Kilim A

Where i can  read about it? I did not create distributor cert only get a request device-profile.xm

I

John Ixion

the certificate howto: https://developer.tizen.org/forums/general-support/how-register-author-certificate-tizen-sdk

Kilim A

This is why certificate is  difficult -

Wearable sdk started  to give the error with build project everytime

 I Reinstall wearable sdk

 But i can use ( requst) my old crt file.

Because we need another files - one of its - author.pri

Marco Buettner

You doesnt need backup/restore the tizen-sdk files, you just need the .p12 file (author certificate) ... thats all ... :) This can u use on Wearable, TV, Tizen2.3 SDK

Kilim A

 

If i simply use .p12  i have signature failed. I known parol and before it works. But old Wearable SDK have problem with build project. May be it is reason of error with signature failed. I don t know

 When i want use old crt file on reinstall SDK Werable on my Win 7 62 i have got that massage ( screenshoot)
 

Marco Buettner

I dont know what are you doing. I use the same .p12 file since Tizen SDK 1.0

Kilim A

i tried use .p12 on 2.3v SDK.  It s not work. Signature Failed

I have alredy told  - two SDK with one workspace is warranty  of incomprehensible errors in SDK work

unfortunately it is impossible  to make certificate for gear in SDk 2.3