Discussion Board

Results 1 to 2 of 2
  1. #1
    Registered User
    Join Date
    Jun 2009

    HELP - signing themes for Sybian

    I'm trying to create a Theme using CarbideUI and get it Symbian signed. I have uploaded it to Symbian and I get an error for using a developer certificate when I should be using a publisher certificate.

    I've looked at the following guides:

    They all seem to be for full blown apps. I simply want to sign my theme and the best explanation of how is below (except I have no programming experience). Why does Carbide have the key pairs option? It seems straight forward but so far it has been a very frustrating few weeks...

    Publisher ID signing
    Copy the private key (private.key) and public certificate (public.cer) files to the same directory as your .PKG file, then add the following line to the .PKG file on the code lines above specifying files to be copied onto the device:
    where **** is the password for the private key. If the private key is not password protected you would add the line:
    See below for a UIQ example .PKG file, where the appropriate code lines have been added:
    ;Header and app name, KExample UID - 0xdeadbeef
    #{"Example-EN", "Example-FR"}, (0xdeadbeef), 1, 2, 3, IU, SH
    ;Supported Platform Definitions
    (0x101F617B), 2, 0, 0, {"UIQ20ProductID","UIQ20ProductID"}
    ;Signing files (and password if applicable)
    ;And finally, the files to install
    Execute MakeSIS as usual to create your .SIS file and you should now have a .SIS file that is signed and ready to be submitted for testing.

    I have no idea what any of that means. The package file in my theme??? Does that mean I shouldn't handle key pairs? This is contrary to the Carbide documentation. please help!

  2. #2
    Registered User
    Join Date
    Jun 2009

    Re: HELP - signing themes for Sybian

    I'm adding the contents of my pkg file, what do I add in here?

    ; File created with SkinCompiler v0.0.82
    ; Installation file for themepackage skin
    ; Package header
    ; Supports Series 60 v3.x
    ; This line indicates that this installation is for the Series 60 platform v3.x
    ; This line must appear _exactly_ as shown below in the sis file
    ; If this line is missing or incorrect,the sis file will not be able
    ; to be installed on Series 60 v3.x platforms
    ; Requires Series 60 Skins Support
    ; Requires Series 60 Scalable Skins Support
    ; Non-localised vendor name
    :"Unknown Vendor"
    ; Localised vendor name
    ; Files to install
    "themepackage.mbm" - "!:\resource\skins\20027103\themepackage.mbm"
    "themepackage.mif" - "!:\resource\skins\20027103\themepackage.mif"
    "themepackage.mbm" - "!:\private\10207114\import\20027103\themepackage.mbm"
    "themepackage.mif" - "!:\private\10207114\import\20027103\themepackage.mif"
    "themepackage.skn" - "!:\private\10207114\import\20027103\themepackage.skn"
    ;Dummy entry for the possible skin .ini file,so that it gets removed on uninstall
    "" - "!:\private\10207114\import\20027103\20027103.ini",FN
    ; End of file

Similar Threads

  1. Series 40 code signing issues with push registry
    By blackbuddha in forum Mobile Java Networking & Messaging & Security
    Replies: 5
    Last Post: 2009-05-21, 13:43
  2. App Signing
    By stevejanko in forum Mobile Java General
    Replies: 9
    Last Post: 2009-04-14, 20:56
  3. Which api's need the signing
    By manojkumar.m in forum Mobile Java General
    Replies: 5
    Last Post: 2008-11-03, 08:29
  4. Signing problem with 6630 and jad file
    By panwoo in forum Mobile Java General
    Replies: 7
    Last Post: 2005-11-19, 14:57

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts