[moved] Cert stopped working

[juhauta]

Wha'ts wrong now. I installed the 3rd pack at the side of 5th one to carbide.
Also had mine cert & key +.sis files from the nokia beta program. Did make couple of apps and they are published and working fine in the Ovi.

My latest app how ever did not work. Cannot install the .sisx even to my own device (that has the developer packet installed) and the previous "signed" .sisx worked fine. Now it says Cert expired.

My idea is that the /sis/myapp.pkg has invalid vendor names.
Do I need to change the .pkg file and what to type in there? is it company Ltd, Company LTD or what..?
Previous apps worked fine without any modification of this file..


http://blogs.forum.nokia.com/blog/ov.../qt-content-qa

[kiran10182]

Since your query is more related to Ovi publishing, I am moving your thread here.

You need to send an email to Ovi publish team and they may help you. But before sending an email, please read this similar discussion on this thread: http://discussion.forum.nokia.com/fo...a-shared-UID-s

[juhauta]

I tested this with another pc also. Same problem.
First I got the cert + 2 uids. Later I got more uids and have been using one of them with success.
How ever something happened now and the signing does not work anymore. Could it be something to do with s603rd extension also installed in the same pc ?

[symbianyucca]

Basically, check that you are signing only unsigned sis files, some older devices did only check the most upper one, but newer devices are checking them all, and if any of the certificate is not valid it gices errors for it. Also you could use signsis to check the sis files certificates and the validity peiod for all signatures in it.

Also do cehck that your time settings are ok in all devices, and propably you could see that your pc has correct date & time as well. And then I'm not certain on what is the "developer packet", and what is has to do with certificate issues.

[tamhanna]

Also do cehck that your time settings are ok in all devices, and propably you could see that your pc has correct date & time as well. And then I'm not certain on what is the "developer packet", and what is has to do with certificate issues.

My friend, the walking, talking Yucca tree, has the problem nailed. AFAIK (my wife handles that in our office), there has been a DST change recently.

Check if: a) Your PC is set to the correct location(!!!), time and date(!!)
b) Check iof your phone is set to the same data, but the time two minutes ahead

Does that fix your issue?

[juhauta]

Thank you for your help!

The developer sis in the phone was update to certs so that my phone accepts the signed .sisx file to be installed. It stopped working.
I did change my date on the phone couple of times, but chaged it back. Already noticed earlier that if the phone's time is one minute earlier than pc, I have to wait before installing.

I don't understand how to check location of pc/mobile ?
Could there be a risen issue that my win XP is english, but phone is finnish. (Hate to use finnish os and programs, but it's nice to be able to type finnish letters like ö and ä )

I'm signing the sis like before when they worked. Using carbide Gui and inserting .key .crt into project's settings..

My pc was slow anyway so now I'm formatting the drive and installing all over again.. tomorrow we'll see that does this help..

[symbianyucca]

the different languages wont matter, I'm only using semi-english laptops (Thai-English, Finnish-English, and currently, partially German-fin-English) with english menu's on, and devices with multiple different language's on them, and never got any problems with it.

the issue is solely on the certificate, and reinstallations most likely would make no difference. Anyway what was the "developer packet" you talked about ?, and did you check and do what was asked since your last post ?

[juhauta]

The "developer packet" was .sis file that Nokia sent when I got my cert. I strongly believe that it enables my phone to install my signed apps. (the .sisx) And it did it before successfully.
Now I installed whole system again, checked versions of Perl etc. and made totally new flash stub c++ project. No errors while building. Also checked the dates & timezone.

When trying to install the "signed carbide c++ made flash stub example" .sisx file in my phone it says "cert no longer valid".
At this point it does NOT help if I adjust the phone's date + - 1 day or -2 months.

---
The problem installing my phone could be that the "developer packet" in my phone does not contain the new uids. BUT this does not explain why my app got approved to OVI and failed to install on customer's phones with the same reason.
I can make .sisx with the "random" uid, 0xe... but that wont help me to get the content into Ovi!

[symbianyucca]

if there is something magic on the sis you need to install to the device, then contact the publicer email to ask for assistance. Actually I'm not official Ovi support, thus would not know what that sis could contain.

anyway, maybe you could try using the signsis to read the certificate(s) in your sis file to see the validity peiod it is having.

[juhauta]

Thank you Jukka for your help. I had emailed ovi support and got new certificate & key files today. After building the same app with them it worked.
The phone developer packet's real name is "developer certificate installer" also got new one of those.

So the conclusion: My cert was expired or it did not support the new range of uids.


Current & fixed:

Primary:
Issued by : OVI Publisher 09-30-2010
Issued to : OVI Publisher 09-30-2010
Valid from 01/10/2010 to 30/12/2010

Old that did not work:
Primary:
Issued by : OVI Publisher 06-28-2010.
Issued to : OVI Publisher 06-28-2010.
Valid from 28/06/2010 to 26/09/2010

If I had just to know that there is tool signsis.exe mysis.sisx -o I havent wasted so much time to try fix the unfixable

[tamhanna]

the different languages wont matter, I'm only using semi-english laptops (Thai-English, Finnish-English, and currently, partially German-fin-English) with english menu's on, and devices with multiple different language's on them, and never got any problems with it.

the issue is solely on the certificate, and reinstallations most likely would make no difference. Anyway what was the "developer packet" you talked about ?, and did you check and do what was asked since your last post ?

Time Zone, I meant.

Sorry for having expressed myself unclearly!

[pixsta]

Thank you Jukka for your help. I had emailed ovi support and got new certificate & key files today. After building the same app with them it worked.
The phone developer packet's real name is "developer certificate installer" also got new one of those.

So the conclusion: My cert was expired or it did not support the new range of uids.


Current & fixed:

Primary:
Issued by : OVI Publisher 09-30-2010
Issued to : OVI Publisher 09-30-2010
Valid from 01/10/2010 to 30/12/2010

Old that did not work:
Primary:
Issued by : OVI Publisher 06-28-2010.
Issued to : OVI Publisher 06-28-2010.
Valid from 28/06/2010 to 26/09/2010

If I had just to know that there is tool signsis.exe mysis.sisx -o I havent wasted so much time to try fix the unfixable

Why are these free certificate's expiration deadlines that short/strict? The certificate works only on 1-5 devices, so the possibility of fraudulent use is almost zero.