|
|
3rd Edition UID 0xExxxxxxx vs. 0x2xxxxxxx
| Fri, 2007-01-05 21:17 | |
|
Hello all.
To develop and test your own self-signed app, you have to be using a UID that starts with E, and then when you turn it in for the final signing process, you have to change the UID to 2. Is this correct? Or can you start using the UID that begins with 2 as soon as you setup your VeriSign account? The reason I ask, is that I think it's rather clumsy to have a application ready for production, and then do a "search and replace in files" to change all the UID numbers. -euroq |
|
Forum posts: 2009
Eric Bustarret
NewLC Founder & CEO / Professional Symbian OS Consultant
Forum posts: 149
Before I was developing with 0xExxxxxxx UIDs and was able to install the app to the device and it ran just fine.
I changed all my UIDs to the 0x2xxxxxxx format, self-signed it with my own random certificate, and tried installing it to the device. I get an "Unable to install a protected application from an untrusted supplier." Which means (according to Google) that it's because my UID is 0x2xxxxxxx.
When I sign it with my VeriSign certificate, it says "Certificate Error." Of course, at this point, I haven't sent it off to VeriSign or whomever tests it yet, so technically it's still self-signed.
But, the point is that I cannot get this app to the device for testing with a UID of 0x2xxxxxxx. So basically, as far as I can tell (please correct me if I'm wrong), is that I develop with the 0xExxxxxxx UID, then right before I send it off to get tested and signed I'll do a file search and replace to change the UID3 to 0x2xxxxxxx. Am I missing something here?
Thanks,
-euroq
Forum posts: 149
1. If you need to install a development app to the device, you can change the settings on the phone to allow untrusted apps to be installed. For these, you can sign them with any randomly generated key/certificate of your own. However, you must use the development UID range (0xExxxxxxx).
2. If you want to test out the app with certain capabilities with the proper UID that you will be getting your application signed with (0x2xxxxxxx), you need to get a developer certificate (DevCert) available from Symbian Signed. Unless you are getting your application signed, you don't need to bother with this. The advantage that I had from using this was that I was able to install the exact same build on my device and test it out before sending it to get signed. (Otherwise, I would have had to change code without testing it on the device).