Symbian Signed: New and improved

[enstedt]

Symbian Signed has changed. Three new and simplified signing options are available to developers, supported by a new (and lower cost) Certificate Authority.

More information available at http://developer.symbian.com/main/signed/.

[mitts]

In particular, pay attention to the new test criteria, a LOT has changed. Also do note that you are expected to follow these same test criteria (doing the tests yourself as part of a professional QA phase in your R&D) even if you submit applications via the Express Signed program.

[dracula78]

In particular, pay attention to the new test criteria, a LOT has changed. Also do note that you are expected to follow these same test criteria (doing the tests yourself as part of a professional QA phase in your R&D) even if you submit applications via the Express Signed program.

Our test team had just worked out all the old test criteria, so they were really happy to hear they could start all over The changes look good, much clearer than before, also covering many exceptions.

When requesting a new Developer Certificate I keep getting an error that the uploaded .csr does not contain any Manufacturer capabilities, which is not true. It even rejects a .csr file I succesfully used several weeks ago.


Edit: Wait a minute, is MultimediaDD no longer a manufacterer capability? How do I then add new IMEI numbers to my current developer certificate if the upload form rejects .csr files? I tried with both the old and the new DevRequest tool, and both with and without ACS publisher ID (in the last case I don't get the option to select MultimediaDD).

With all these new options, I begin to lose the overview on how to get our application signed. First for development, second for testing SymbianSigned criteria, third for release.

[enstedt]

Our test team had just worked out all the old test criteria, so they were really happy to hear they could start all over The changes look good, much clearer than before, also covering many exceptions.

When requesting a new Developer Certificate I keep getting an error that the uploaded .csr does not contain any Manufacturer capabilities, which is not true. It even rejects a .csr file I succesfully used several weeks ago.


Edit: Wait a minute, is MultimediaDD no longer a manufacterer capability? How do I then add new IMEI numbers to my current developer certificate if the upload form rejects .csr files? I tried with both the old and the new DevRequest tool, and both with and without ACS publisher ID (in the last case I don't get the option to select MultimediaDD).

In this case you will need to do a new DevCert request with the MultimediaDD capability to the general Symbian Signed process. Updating an existing and approved DevCert with new IMEIs -enhancement is only available when requesting manufacturer DevCerts from Nokia. And in the new Symbian Signed process, only DevCerts including AllFiles, DRM or TCB will go through this manufacturer path.

[dracula78]

Thanks, indeed a normal DevCert worked fine, had almost forgotten about that option. It is good to see MultimediaDD more easily accessible.