Platform UID

The platform UID for S60 5th Edition is 0x1028315F.

The UID is specified as a requisite in the installation package file (.pkg). To add the UID, include the following line in the .pkg file of your application:

[<UID of compatible platform>], 0, 0, 0, {"Series60ProductID"}

The values used in the above are:

Value

Description

[<UID of compatible platform>]

The UID of the platform version that the application is compatible with (S60 3rd Edition and later versions).

For example:

  • 0x1028315F for S60 5th Edition

  • 0x102752AE for S60 3rd Edition, Feature Pack 2

  • 0x102032BE for S60 3rd Edition, Feature Pack 1

  • 0x101F7961 for S60 3rd Edition

(<UID of compatible platform>)

The UID of the platform version that the application is compatible with (S60 2nd Edition, Feature Pack 3, and earlier versions).

  • 0x102032BF for S60 2nd Edition, Feature Pack 3

  • 0x10200BAB for S60 2nd Edition, Feature Pack 2

  • 0x101F9115 for S60 2nd Edition, Feature Pack 1 (v2.1)

  • 0x101F7960 for S60 2nd Edition (v2.0)

  • 0x101F6F88 for S60 1st Edition (v0.9)

0, 0, 0

This is an unused version field; it must always be defined as (0,0,0).

{"Series60ProductID"}

This is the name of the dependency. It is not used by the S60 platform, but this string will be displayed as part of an error message in the user interface of a non-S60 Symbian OS device if an attempt is made to install the .sis file. It is possible to supply multiple strings if the installation package is multi-lingual.

In S60 5th Edition, the platform UID must be defined with square brackets in the .pkg file. If defined in round brackets, as in S60 2nd Edition, FP3, and earlier versions, the platform UID is not recognized by the installer and installation of .sis file fails with an “Application not compatible” error. Please note that some tools or IDEs that are capable of automatically creating .pkg files for S60 5th Edition projects may still incorrectly use round brackets for the dependency line.

S60 C++ APIs are commonly targeted at multiple platform versions. Thus, it is worthwhile to design the application for multiple platform releases. Choosing the correct Platform UID helps in declaring the compatibility of each application build. The general rule is that you should use the Platform UID of the first compatible S60 platform release to provide smooth installation on that and all subsequent platform releases (provided that there is no binary break between platform releases).