A software engineer living in Vancouver, Canada - http://www.antonypranata.com/
antonypr | 16 June, 2006 22:38
If you have been reading discussions at Forum Nokia Developer Discussion Board recently, you may notice there are many questions about signing in S60 3rd Edition. It seems the new security feature in Symbian 9 has led to frustration for some developers.
I would like to share what kind of error messages I have seen when installing signed/unsigned application in S60 3rd Edition phones. There is a hint that explains what may cause a particular message. I may not be able to cover all error messages because I may not have seen all of them.
Message: Certificate error. Contact the application supplier.

Hint: You may have tried installing unsigned application. Note that signing is mandatory S60 3rd Edition. You can use self-signed certificate or developer certificate from Symbian Signed to sign your application.
Message: Unable to install. Constrained by the certificate.

Hint: This message pops up when you attempt to install developer certificate in the unsupported device. The developer certificate from Symbian Signed can only be used in a limited number of devices. Remember that you have to send your IMEIs to Symbian Signed when requesting certificate. You cannot use the certificate in other devices that is not in your IMEIs list.
Message: Required application access not granted
Hint: Check that your certificate can be used to sign all capabilities needed by your application. For example, if you use self-signed certificate, you can only sign basic set capabilities, i.e. NetworkServices, ReadUserData, WriteUserData, LocalServices and UserEnvironment. If your application requires one of the extended capabilities, for example SwEvent, you cannot sign it with self-signed certificate. In this case, apply for developer certificates from Symbian Signed.
Message: Unable to install a protected application from an untrusted supplier

Hint: If you use self-signed certificate, make sure that your application uses unprotected UID, i.e. 0xA0000000 - 0xAFFFFFFF. If you use protected UID (0x20000000 - 0x2FFFFFFF) or legacy UID (0x10000000 - 0x1FFFFFFF), you will get this message.
Message: Unable to install

Hint: This message may come up when your installation file (.sis/.sisx) copies files to other application's private folder, i.e. privateuid. Note that Symbian 9 introduces data caging concept, it means you don't have access to other application's private folder.
mgroeber9110 | 27/06/2006, 16:05
mikkoiv | 14/07/2006, 16:23
SlonUA | 07/11/2006, 15:07
symbee | 21/07/2006, 13:22
chall3ng3r | 02/04/2007, 11:27
"Installer Feature Not Supported!" error is shown when you compile your project using latest feature pack, and running the app on earlier version.anorland | 05/08/2006, 00:55
winfoware | 18/08/2006, 17:42
alsaleem | 29/08/2006, 06:23
bnvaikos | 30/11/2006, 10:40
bnvaikos | 04/12/2006, 12:50
davidmaxwaterman | 19/09/2006, 21:58
sainedi | 02/11/2006, 00:07
antonypr | 02/11/2006, 18:01
This is really weird. It seems that some of you devices cannot recognize your certificate.thedawn1977 | 30/11/2006, 18:44
antonypr | 01/12/2006, 17:51
Shahar, thanks for the clarification. You're right, this may cause a problem too in Symbian 9.
rathodavinash | 02/11/2006, 15:14
antonypr | 02/11/2006, 17:57
You need so specify the output file name. So, the command should look like this:SlonUA | 07/11/2006, 14:53
stodolni | 14/10/2007, 12:58
antonypr | 14/10/2007, 19:49
You may try the trick described in my other blog, http://www.s60tips.com/2007/01/03/deleting-stuck-installer-files-in-s60-3rd-edition/bm | 13/11/2006, 07:21
antonypr | 13/11/2006, 08:59
The "uninstalled" one is just some kind like cache (that's my understanding). You can remove it safely. I also notice this happens several times, but don't realy know what causes it.
antonypr | 30/11/2006, 17:54
I just noticed recently this may happen for example if you transfer .sis files to your phone and then you cancel the installation in the middle. The uninstalled .sis file will be available on the phone. Not sure if this is by design or bug though.
stellion | 08/12/2006, 03:38
antonypr | 08/12/2006, 10:55
How about the default UID from Hello World application (0xA000017F)? Does it work?stellion | 08/12/2006, 21:42
antonypr | 12/12/2006, 23:14
I put a link to Forum Nokia Discussion that is related to this problem so that everybody can track it too,
antonypr | 14/12/2006, 23:48
Ops sorry... forgot to put a link, http://discussion.forum.nokia.com/forum/showthread.php?t=79269
samuel.weibel@ascom.ch | 18/12/2006, 10:46
cartman_ume | 02/01/2007, 16:50
acadiano | 08/02/2007, 08:19
antonypr | 08/02/2007, 08:26
Normally that happens if your date on the phone is incorrect. Sometimes if happens if your certificate has future time (compared to your phone's time). Just check your certificate date and your phone's date.
edc088 | 26/07/2007, 18:08
antonypr | 26/07/2007, 18:47
There are two things you may want to check.cezaryk | 08/08/2007, 13:28
litenbubbly | 21/10/2007, 05:18
ss7guru | 29/10/2007, 18:02
When I run the signsis I get "cannot read WorldCert.cer". The cert was generated with makekeys and the .cer and .key are in the directory with the .sis I want signed.
Any clues?
ss7guru | 29/10/2007, 19:13
William | 01/11/2007, 14:09
Often with devcerts you got Unable to install if time on your device in wrong.
Saritha Reddy | 19/03/2008, 07:43
Hi, I m trying to instal a simple hello world application on E61i, it is throwing message "Unable to install a protected application from an untrusted supplier" I m having default UID of helloworld i.e 0xA000017F.
Help me how to clear this error.
BR,
Saritha
bytes | 27/03/2008, 17:04
Antony & all,
I have the same problem.
====================================
I am getting this error "Unable to install. Constrained by the certificate.", above you have the hint that the IMEI is not in the certificate, but I have checked this twice and still get this error, what else can it be?
================================
But strangely its installed on some devices and not on some devices.
And those IMEIs are newly added. Its woking on old IMEIs.
We got Publisher ID from Trust Centre.
I am using the following capabilities.
NETWORKSERVICES
READUSERDATA
WRITEUSERDATA
NETWORKCONTROL
WRITEDEVICEDATA
READDEVICEDATA
USERENVIRONMENT
MULTIMEDIADD
SwEvent
I am using latest Symbian Development certificate request Wizard.
thanks for yout time
A software engineer living in Vancouver, Canada - http://www.antonypranata.com/
RDF Facets:
qfnZtopicQUqfnTopicZcppQ
qfnZtopicQUqfnTopicZseriesE5f60Q
qfnZtopicQUqfnTopicZtestingQ
qfnZtypeQUqfnTypeZBlogContentQ
qfnZtypeQUqfnTypeZBlogE45ntryQ
qfnZtypeQUqfnTypeZCommunityContentQ
qfnZtypeQUqfnTypeZWebpageQ
qmarsZlanguageQUxhttpE3aE2fE2fswE2enokiaE2ecomE2flanguageE2d1E2fenX
Re: Interpreting Platform Security Error Messages in S60 3rd Edition
samposuv | 20/06/2006, 18:37
This is very useful and relevant information, thank you. It's a pity that these error messages are still on the same level as error messages were in the 1980s! A lot more could be done very easily at the operating system level (if they just read Alan Cooper's book). This would help development and save everyone's time.
In the beginning these cryptic minimalistic error messages do cause a lot of confusion. Everything seems correct and your phone just keeps telling you that you are untrusted. Or that he is unable to install. With no further hints whatsoever. It could easily say, for instance: "You are trying to install a self-signed application but your UID is on the protected range. Please change your UID to the unprotected range and try again."
Two more hints for developers:
1. During development sometimes it helps to go the App.Manager and uninstall a previously installed (specially if the installation has failed which often creates strange dirty remnants) version of your application. It may be the cause why your newer version can not be installed. I don't know why this happens, but we have seen this on a number of occasions.
2. Sometimes uninstalling is not enough. If all else fails, a very useful short code is *#7370#. It resets the phone to factory settings and some 30 seconds later you are ready to install any test version again. If the error message was indeed caused by a previous version you will not get an error message any more. At least for one round of testing...
By the way, the 'lock code' for doing the factory reset operation *#7370# is usually 12345.