From Symbian Developer Community

Run through the test criteria before you submit

The test criteria apply to every application. So whether you're using Express Signed or Certified Signed, running through the test criteria before you submit will save you failures later on. If your application doesn't pass the tests, then raise a question on the support forum or talk to the Symbian Signed team before you make your submission.

Provide all the correct information when you submit

Sometimes the test house will need a bit of extra information in order to test your application - maybe a password, or a test harness or access to a particular network or service. If this applies to you, make it clear in your readme.txt and you won't have to spend time dealing with the test house later on when they can't test your application. This applies to both Express Signed and Certified Signed.

Get your application UIDs correct

Get UIDs from the protected range using your Symbian Signed account when developing your application. Make sure that you own the UIDs you're using for your application. Also, make sure that you've changed the UIDs throughout your project before you build it and create your .sis file. The most common reason for applications not installing after signing is that the developer hasn't changed the UIDs correctly throughout the project.

Get the platform UIDs correct

Understand the lead device table and which phones will be used to test your application. Only put in the UIDs of platforms that your application is designed to work on.

Don't stop the task manager being used to kill your application

Unless there's a very good reason for it, you should allow your application to be killed by the system task manager. If your application appears in the task manager, then the user must be able to kill it from there.

Provide a way for the user to turn off auto-start functionality

If your application needs to start when the phone boots, you must provide a way for the user to turn this feature off. You can do this by providing a check box in your application settings dialogue. This is one of the most common test failures, and is easily avoided.

Clean up when your application is uninstalled

When your application is uninstalled, it should clean up after itself. If your application is designed to leave data behind on the device, then make it clear in your readme.txt file what data is left behind and why. It's acceptable to leave downloaded content on the device, or even a text file to enforce the terms of a trial period of the application, but make sure you declare it when you submit otherwise you'll fail the uninstall test.

Make sure your Publisher ID organisation name matches the one in your account

You will fail testing if you Publisher ID was registered by a different organisation to the one listed in your account. You should check this before you submit, and if you have a problem complying with this, please contact symbiansigned@symbian.org to discuss it before you make your submission.

Cooperate with the test house if they contact you

Sometimes the test house will need some more information from you. They'll send an email to the email address given during submission and you should respond to them giving them the information they need. You can avoid the test house having to contact you at all if you provide all the information in your readme.txt file. The worst thing you can do is ignore the test house when they contact you, as that will lead to you failing the audit.

Use the Symbian Signed Support Forum

If you're still unsure about how to get through Symbian Signed testing, then go to the forums at http://developer.symbian.org and check out the Symbian Signed Support forum. The Symbian Signed team at Symbian and other community members will answer questions quickly, and there's a chance that someone else will already have asked the same question and so you can get an immediate answer.

Comments

Sign in to comment…