How to sign applications for RDA devices using a RDA specific developer certificate
Use the method described in this article to sign your application for testing on any Symbian device connected to the Nokia Developer hosted Remote device access (aka RDA) service. The certificate includes the IMEIs of all RDA devices by default, so you will only need to sign your installation package once and it should work across the devices.
Keep in mind that the provided RDA developer certicate is only intended for RDA use/testing phase and does not work elsewhere. The certificate includes all Symbian capabilities except those that require manufacturer approval (so AllFiles, DRM & TCB are excluded).
Note the signing process described here works only for .sis packages, it does not apply to MIDlets or any other content types
Article Metadata
Contents |
Installation
1. Login to the RDA with your Nokia Developer username, go to “Phones”-view and click the “Download dev cert for RDA devices” button. The resulting RDA_devcert.zip contains rda_certificate.der, rda_private-key.pem and rda_cert.sisx files. The certificate and key files you’ll be needing in any case, the rda_cert.sisx is for installing the certificate on the remote device (see Troubleshooting for details).
Additionally you’ll need signsis (it is included with the Symbian SDK). If you are using command line for the signing the syntax is the normal “signsis myUnsignedApp.sis mySignedApp.sisx rda_certificate.der rda_private-key.pem”. The RDA developer certificate is updated whenever changes are made to the RDA device base, so make sure you always download the up to date version of the certificate before proceeding with signing/testing.
Alternatively for example Qt Creator provides an option to sign your application at the build step. In that case you’d just select the “custom certificate” option and define the certificate location there.
2. Now the application (Sensors_5x.sisx in this example case) should be installable to RDA devices. Reserve a wanted test device and install the application to the device.
3. Application installed ok!
Troubleshooting
If you face installation problems, the first thing to do is to make sure is that the phone date and time settings are correct.
Secondly you should verify that up to date root certificate version is present on the device. Check this by navigating the menu to Settings -> Phone -> Phone Management -> Security Settings -> Authority Certificates. The certificate should be listed with name "RDCert1" (the currrent valid version is RDCert1 RDA_testing-10212488-4). If it's missing you will need to use the the included “rda_cert.sisx” to install it to the device yourself.
If there is already a "Nokia R&D certificate provisioner" application installed on the device, but a valid root certificate version is still missing, first uninstall the certificate provisioner application from the device and only then use the provided rda_cert.sisx to install the root certificate to the device. After that the process should work.
If you face other related issues, you report them to the RDA admin (ndh.fi@nokia.com).






Contents
Don chohan -
hey i cant find any certificate in Authority certificates but its in trusted site certificatesdon_chohan 12:49, 10 September 2011 (EEST)
Pgarofalo - Directions Incomplete?
I've followed the instructions above but when I try to build (in Qt Creator I click Run, because the Build command apparently does not generate SIS files) I get "ERROR: signsis failed at C:\QtSDK\Symbian\SDKsSymbian3Qt473\bin\createpackage.pl line 391." The line in this perl script is
system ("${epocToolsDir}signsis $unsigned_sis_name $signed_sis_name $relcert $relkey $passphrase") and die ("ERROR: signsis failed");It fails with an error # 2, which is file not found. I've tried building with Smart Installer option on and off and by clicking the Clear Passphrase button. Before building I did a Clean of the project and also ran qmake. What could be causing this error?
When I select self-signed for the project it builds and runs without error. The signsis.exe file is present in the following places C:\QtSDK\Symbian\SDKs\Symbian1Qt473\epoc32\tools C:\QtSDK\Symbian\SDKs\Symbian3Qt473\epoc32\tools C:\QtSDK\Symbian\SDKs\Symbian3Qt474\epoc32\tools C:\QtSDK\Symbian\SDKs\SymbianSR1Qt473\epoc32\tools
I've tried setting the system environment variable EPOCROOT to appropriate path as expected by the epocToolsDir variable in the failing line, but this made no difference. (The SDK installation did not create this environment variable so it must be done elsewhere in the build script, but I thought I would try anyway.)
The instructions above say nothing about UID3 settings. Are the standard self-signed UID3 values provided by Qt Creator valid for RDA testing? Are there different values needed specifically for RDA testing?
Running from the command seems to be non-starter for Qt Creator generator apps.
Thanks for reading. Any additional information is appreciated.pgarofalo 19:44, 9 December 2011 (EET)
Hamishwillee - This is probably failing because signsis can't find your unsigned sis file
Either:
hamishwillee 02:13, 14 December 2011 (EET)
Pgarofalo - Can't have spaces in the certification and key file paths
Hammish, thanks for your suggestions. I discovered that the problem is due to a space in the directory path specifications for the certificate and key files. The devcert files have to be in a folder whose path specification has no spaces.pgarofalo 01:43, 15 December 2011 (EET)
Amoormagdi -
i cant open the RDA devicesAmoormagdi 22:15, 2 January 2012 (EET)
Atphalix - Linux compatible?
is it possible to sign under Linux?atphalix 23:17, 16 June 2012 (EEST)