Publishing Applications to Ovi Store

The process and requirements to publish Qt applications to Ovi Store are described in the Guide to Publishing Qt Applications to the Ovi Store wiki.

This section describes, how to use Qt Creator to generate SIS packages that you can publish to Ovi Store.

Publishing Qt Content for Symbian Devices

You can use the Application Signing Services for Ovi Store to get your application Express Signed for free by Nokia. Make sure to use the application UID that you receive from Ovi Publisher Support. Then create an unsigned SIS package and submit it to signing. When you receive the signed package back, package it with Nokia Smart Installer for Symbian before submitting it to Ovi Publishing.

If the application uses functions that require advanced capabilities, you must use the standard Symbian Signed process to have the application Symbian Signed (using the Certified Signed path or the manufacturer-specific channel).

To create a SIS package that you can submit to Ovi Publishing:

1. Make sure that the source directory is clean. For example, if you use git, enter the following command:

   git clean -dfx

2. Click Projects to edit the Build Settings for the Symbian Device target.
3. Select the Release configuration.
4. Open the Run Settings.
5. In the Create SIS Package step, select the Not signed option.
6. In the Deploy SIS Package step, click Remove Item to skip the step of copying the SIS file to a device. The SIS file is created in the project folder.

   

7. Check that the project .pro file uses the correct UID for the application and the correct vendor information, as illustrated by the following code snippet:

    symbian {
         TARGET.UID3 = 0x2000D7D1
   
         vendorinfo = \
         "%{\"CustomVendor-EN\"}" \
         ":\"CustomVendor\""
   
         my_deployment.pkg_prerules = vendorinfo
         DEPLOYMENT += my_deployment
     }

   Note: Ovi Store does not accept the application if the localized and non-localized vendor information in the package file do not match the publisher name. That is, it cannot be Nokia, Vendor, or Vendor-EN.

8. Choose Build > Run Project.
9. Submit the created .sis file to Application Signing Services for Ovi Store for certification.

   Note: Ensure that your application complies with the Ovi Store publishing requirements.

10. After receiving the signed .sis file from Ovi Publisher Support, copy it over the old application.sis.

    Note: The instructions below assume that you have installed Qt SDK.

11. To package Nokia Smart Installer for Symbian with the application, choose Start > Qt SDK > Symbian > Qt for Symbian Command Prompt to open the Qt command line environment.
12. Change to the project directory. For example:

    cd C:\Sources\Application

13. To create a Smart Installer wrapper package, enter the following command:

    C:\Sources\Application> make ok_installer_sis QT_SIS_CERTIFICATE=publisherid.cer QT_SIS_KEY=publisherid.key

14. Submit the created wrapped .sis file, application_installer.sis, to Ovi Publishing as a Qt Content item.

Note: After you change the application UID, you must use the developer certificate-key pair that you receive from Ovi Publisher Support for testing the application on devices. Self-signing cannot be applied when UIDs from the trusted range 0x2xxxxxxx are used. For more information, see UID.

Publishing Qt Content for Maemo Devices

The applications that you publish on Ovi Store, must meet the testing criteria listed in Maemo 5 Applications: Ovi Store Entry Requirements.

Make sure that your application passes the following most commonly failed test cases:

• Package filename must include the application name and version number using three digits. For example: myapplication_1_0_1.deb
• Application files must be installed to the opt folder on the ext3 partition.
• Debian packages must be given the category user/hidden.
• Application cannot crash or hang during use.
• The application must handle different memory situations correctly.

You set the application name and installation folder in the Run Settings for the project. For more information, see Deploying Applications to Maemo Devices. Qt Creator specifies the correct category settings by default when it creates the Debian directory and the necessary files.

You can test the application on Qt Simulator and Maemo Emulator to make sure that it does not crash or hang and to check how it handles different memory situations. Before you submit the application to Ovi Publishing, you must also fully test it on a Maemo device.