Join Now

Hi, I'm Paul, but you can also call me Todd and I won't get upset.

Uid's and Symbian Signed

Paul.Todd | 07 March, 2008 13:55

Here is a quick review of the UID strategy in Symbian and how it applies to Symbian Signed.

Everything you need to know is in the link below thanks to Dave Mery:

http://developer.uiq.com/forum/entry.jspa?entryID=114

This post is born out of frustration seeing the same questions on both the Symbian and Nokia boards, though strangely enough not NewLC? (what's Eric doing right?)

I am not going to cover the arguments or reasons for this, it is a factual post as I undertand it regarding UID's (See disclaimer at the end)

0xAxxxxxxxx is for applications that are self signed. The UID is requested and associated with a Symbian signed account. This prevents different applications using the same UID and assists tracability when redistributed. Specifically it is for applications requiring only user grantable capabilities. From FP2 this includes Location. By default the certificate has a life of a year. There is a patch here to extend it.

0x2xxxxxxx range is for applications that must be Symbian signed by the licenced owner because they are using Extended Set capabilties. The UID is associated with a Symbian signed account. This prevents different applications using the same UID. Specifically it is intended that ALL applications in this range will be Sybmbian Signed BEFORE being redistributed publically.

0x1xxxxxxx -
0x0xxxxxxx range is for internal testing use only and should requires a publisher id to use. This is primarily for integration work with pre OS 9.x components and will not be Symbian Signed or redistributed

0XExxxxxx range is internal testing applications/prototypes/Proof of concept. These UIDS are for internal test applications requiring enhanced set capabilties. These uids are NOT associated with an email account and they are intended just for the developers personal machine as UID clashes can and will occur. Specifically these applications should not be redistributed at all. If you are not using any extended set capabiltiies, use a self signed certificate There is an update here to allow self signed sis files to have their certificate life extended from the default


Now some common questions in my inbox:

Can you give me a devcert for <imei> - NO

Please sign <pirated application> - NO

Please sign <freeware application> - NO

This is unfair to developers - Sorry nothing I can do about it and you are asking the wrong person, I don't work (and never have) at Nokia, UIQ or Symbian.

Freeware signing is slow and unreliable - as previous question... 

My program has too many bugs to get through signing - as previous question... 

"FAILURE: Submitted .sis file uses a UID that is not allocated to the account holder matching this email address (0x0000000 )" - email the developer of the application with your IMEI and see if he will sign it for you, I can't, see answer to "unfair for developers".

 As usual I want to point out this is MY understanding and may or may not be correct. Specifically it is not any official point of view of any company I may be or have been associated with.

 

 

S60, Symbian C++, Testing | Next | Previous | Comments (2) | Trackbacks (0)

Comments

Re: Uid's and Symbian Signed

ltomuta | 07/03/2008, 16:56

ltomuta

Well done Paul. The synthesis is correct but again I fail to understand why you know this and I know this, yet so many others simply cannot get it...

Re: Uid's and Symbian Signed

antonypr | 07/03/2008, 20:17

antonypr

I cannot get it at the beginning because the documentation at Symbian Signed page was a bit vague. At least, when I read it, I misunderstood it (or may be because I'm not an English native speaker).

For example, when they mention to use, Open Signed Online, the UID has to be from protected range; otherwise the email address has to match the owner. When I read this paragraph, I was thinking unprotected range should work then. Apparently, it is not.

Anyway, good posting Paul.

You must login to post comments. Login
 
 
Powered by LifeType 
     
     RDF Facets:
     
     
     qfnZtopicQUqfnTopicZcppQ
     qfnZtopicQUqfnTopicZseriesE5f60Q
     qfnZtopicQUqfnTopicZtestingQ
     qfnZtypeQUqfnTypeZBlogContentQ
     qfnZtypeQUqfnTypeZBlogE45ntryQ
     qfnZtypeQUqfnTypeZCommunityContentQ
     qfnZtypeQUqfnTypeZWebpageQ
     qmarsZlanguageQUxhttpE3aE2fE2fswE2enokiaE2ecomE2flanguageE2d1E2fenX