From Forum Nokia Wiki

Contents 1 Introduction 2 What to submit in the ZIP file 3 What to submit for a pre-installed application 4 Submission Tips 4.1 Symbian Signed Checklist

Introduction

1. Visit the Symbian Signed website at http://www.symbiansigned.com
2. Log in using the username and password you created when you first registered.
3. Select ‘My Symbian Signed’ tab at the top of the page.
4. Then select ‘Applications’ on the left hand menu, and ‘Submit’ (if the application is intended to be freeware then please follow the freeware link).
5. Select the test house you require to test your application.
6. Once you have selected a test house you will be shown your user information. You can add or edit information for this specific submission if you wish. Note that changing any details during this step will result in a change to your main account details.
7. You must now submit your application details including the application name, a description and which phone(s) it runs on.
8. Finally, you must submit the actual application itself and supporting materials (see ‘what to submit’ below for details).

What to submit in the ZIP file

The following files/documents are required to be included in the ZIP file you submit.

• Your SIS file (only signed with your Publisher ID). This will be tested by the test house, and, if successful, the SIS file will be re-signed with a unique application certificate and returned to you for distribution.
• The PKG file used to create the SIS file. This will be cross-referenced by the test house to ensure correct target platform and specification.
• A completed Readme.txt or a user guide in PDF format. This should include any release notes and quick advice on how to use the application (OR a separate user guide should be included within the ZIP file in its own right).

What to submit for a pre-installed application

For a PA-type sis file submission you will need to also submit the binaries. Please submit them within a zip archive in the "Test file" submission step, the final step of the submission.

• zip1: PA-type sis, pkg used to create the pa-type SIS, the user guide or readme.txt
• zip2: Binaries in the other zip must be placed inside a folder structure similar to that in which they will be placed onto the memory card.

The PA-type sis must be named according to the naming guidelines and it must have the same version information as a corresponding SA-type sis would have. Note also that the name and version information must be the same as declared in "About".

E.g.

testapp_nokiaN71_v_1_3_0_PA.sis
or
 testapp_S60_3_0_v_1_3_0_PA.sis

Submission Tips

It is in your interests to ensure everything you submit is likely to pass the testing process. Therefore be sure that you have completed the following steps.

• Read the testing specification and guidelines available on the Symbian Signed website and ensure your application follows the provided guidelines. Avoid submitting an application that you know will fail a test – unless you have a relevant waiver(s) in place. Equally, avoid using the testing process as a way to test your application in the hope of finding any failures or

defects – this is not a cost-effective method of bug fixing!

• Prior to signing the application with the Publisher ID verify that the SIS file you are supplying does install correctly on the phone(s) you require it to be signed against. When you have signed the application with your Publisher ID the application will not install on the majority of handsets until Symbian Signed.
• Verify that the ZIP file you are about to submit contains all the required files and completed documentation.
• To get a debugging and style report on your SIS file, you may want to check it on WTFWMSFI?. WTFWMSFI highlights formatting and stylistic issues in your SIS file, and giving you clear advice in plain English on how to fix them.

Symbian Signed Checklist

• Ensure correct spelling and grammar throughout your resource files and any user-visible text.
• Help files included in the SIS file (if applicable).
• 'About' screen with correct version information, etc.
• Consistent terminology with phone/UI and/or other industry applications.
• Ensure application operates in accordance with any supplied documentation.
• You have correctly applied UI style guidelines in your application as recommended by the SDK provider.