×
Namespaces

Variants
Actions
Revision as of 09:09, 6 March 2012 by hamishwillee (Talk | contribs)

Publishing Qt apps to the Nokia Store

From Nokia Developer Wiki
Jump to: navigation, search
Article Metadata
Compatibility
Platform(s):
Symbian
Article
Created: OviKevin (29 Jan 2011)
Last edited: hamishwillee (06 Mar 2012)
Featured Article
13 Feb
2011

Contents

Guide to Publishing Qt Applications for Symbian to the Nokia Store

Pre-requisites:

  1. Register as a publisher to Ovi Publish
  2. For signing your application during R&D phase you need a Developer Certificate, which can be obtained from Nokia Publish (see the free signing offer, terms and conditions apply) or from Symbian Signed (more flexible but not free, see Developer Certificate (Symbian Signed) ).
  3. Develop and Test your Qt application.

Steps:

1.) Select a signing service for signing your application:

Option a.): Application Signing Services for Ovi Store (recommended): Nokia offers a free signing service for applications for the Ovi Store.

  • Steps:
  • Restrictions for Nokia Signed:
    • Application can only use User and/or System Capabilities .
    • Only for Ovi Store distribution.

Option b.): Symbian Certified Signed: for applications that require Restricted and/or Device Manufacturer Capabilities.

Option c.): Symbian Express Signed: for applications that require User and/or System Capabilities and distribution to other channels.

2.) Package your Qt application with the Nokia Smart Installer (Nokia Qt SDK 1.1):

3.) Follow the Packaging requirements for the Ovi Store.

4.) Ensure your application adheres to the Guide to Publishing Qt Applications to the Ovi Store, which is listed below.

5.) For applications requiring signing via Symbian Express/Certified Signed, submit application to the Symbian Signed Portal for signing.

6.) Submit your application to Ovi Publish: Publisher Guide link

Qt Application Packaging Inspection Checklist

Qt applications for the Ovi Store undergo a package file inspection process during QA to ensure the application will install correctly on all the devices that support Qt. This section details what is analyzed during the inspection process.

Please note the mandatory elements in the example wrapper and application .pkg file listed below. The mandatory elements are numbered and italized.

Wrapper .pkg (MyApplication_installer.pkg) file

Sis header:

1.) UID must be 0x2002cccf

2.) Version number must match the version string displayed in the application.

#{"My application installer"},(0x2002CCCF),1,0,0


3.) Localised Vendor name - Must specify publisher name. Link for more instructions

 
%{"Publisher name"}


4.) Unique (Global) Vendor name - Must specify publisher name. Link for more instructions

 
:"Publisher name"


5.) Platform Compatibility - Modify to control the set of platforms/devices your application supports. For more info, please refer to PKG file format and S60 Platform and device identification codes"

[0x101F7961],0,0,0,{"S60ProductID"}
[0x102032BE],0,0,0,{"S60ProductID"}
[0x102752AE],0,0,0,{"S60ProductID"}
[0x1028315F],0,0,0,{"S60ProductID"}
[0x20022E6D],0,0,0,{"S60ProductID"}


6.) Location of Qt application .sis must be !:\private\2002ccce\import\. Older versions of Qt Creator and Carbide.c++ placed the Qt application .sis in c:\adm\, which is incorrect. Note: The Smart Installer does not support space characters in the file name of this SIS file, so ensure there are no spaces in the file name.

"MyApplication.sis" - "!:\private\2002CCCE\import\MyApplication.sis"

7.) Dependency to Qt Smart Installer

@"C:/NokiaQtSDK/Symbian/SDK/smartinstaller.sis",(0x2002CCCD)

Qt application .pkg file:


SIS header:

8.) MY_ASSIGNED_UID, a UID from the protected range assigned either by Publisher Support (if the application is going to be signed by Nokia) or Symbian Signed(if the application is signed by Symbian Signed). Link for more instructions

#{"My application"},(MY_ASSIGNED_UID),1,0,0

9.) Localised Vendor name - Must specify publisher name. Link for more instructions

%{"Publisher name"}

10.) Unique (Global) Vendor name - Must specify publisher name. Link for more instructions

:"Publisher name"


11.) Dependency to Qt Core, Qt Mobility*, and Qt Webkit* libraries (* if used). Specifying an unsupported version will lead to a QA failure. Link to the currently supported Qt release and package version mappings

(0x2001E61C), 4, 7, 3, {"Qt"}
(0x2002AC89), 1, 1, 3, {"QtMobility"}
(0x200267C2), 4, 8, 0, {“QtWebkit”}

12.) Dependency to In-App Purchase* or Ovi Notifications* library (* if used).

(0x200345C8), 0, 1, 1, {"IAP"} 
(0x2002eab4),1, 1, 10480 ,{"Ovi Notifications API"}

"13.) Platform Compatibility - Modify to control the set of platforms/devices your application supports. For more info, please refer to PKG file format and S60 Platform and device identification codes"

[0x101F7961],0,0,0,{"S60ProductID"}
[0x102032BE],0,0,0,{"S60ProductID"}
[0x102752AE],0,0,0,{"S60ProductID"}
[0x1028315F],0,0,0,{"S60ProductID"}
[0x20022E6D],0,0,0,{"S60ProductID"}

14.) Qt application executable and default resource files. [Removed for brevity].

221 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.

 

Thank you!

We appreciate your feedback.

×