×

Discussion Board

Results 1 to 6 of 6
  1. #1
    Registered User
    Join Date
    Jan 2011
    Posts
    3

    DEPLOYMENT += makes installer_sis to fail

    Hi,

    My problem:
    I have a pro like this:

    symbian {
    TARGET.UID3 = 0xxxxxxxxx
    DEPLOYMENT.installer_header = 0x2002CCCF

    ICON = images/symbian/icon.svg

    TARGET.CAPABILITY = NetworkServices \
    Location

    LIBS += -lavkon -lcone

    vendorinfo = Matthieu
    my_deployment.pkg_prerules = vendorinfo

    DEPLOYMENT += my_deployment
    }


    When i try to create the app_installer.sis from cmd line with the next instructions:

    C:\Sources\Application> make distclean
    C:\Sources\Application>qmake && make release-gcce
    C:\Sources\Application>make installer_sis


    I get an error:
    Processing app_installer.pkg...
    wcd_guide_installer.pkg(29) : error: unknown line

    file I/O fault, cannot open wcd_guide_installer_unsigned.sis.

    SIS creation failed!


    Also, I noticed that if I don't add "my_deployment" to DEPLOYMENT, everything works fine.

    My questions:
    - where is the error?
    - will my app be accepted on OviStore without the vendor information in .pro?

    Thank you very much, I will be grateful for any answer.

    Alex

  2. #2
    Super Contributor
    Join Date
    Nov 2009
    Location
    Minnesota, USA
    Posts
    3,209

    Re: DEPLOYMENT += makes installer_sis to fail

    What is this:
    DEPLOYMENT.installer_header = 0x2002CCCF
    I've never seen that construct before.

    It would help if you listed the actual error.

  3. #3
    Registered User
    Join Date
    Jan 2011
    Posts
    3

    Re: DEPLOYMENT += makes installer_sis to fail

    Could be this the error?

    In nokia example I saw:

    symbian {
    TARGET.UID3 = 0xE4DE5D27
    DEPLOYMENT.installer_header=0xA000D7CE

    vendorinfo = \
    "%{\"CustomVendor-EN\"}" \
    ":\"CustomVendor\""

    my_deployment.pkg_prerules = vendorinfo
    DEPLOYMENT += my_deployment
    }


    The only difference is the UDID.

    Don't know if this is the error, but defintely the UDID used by me is wrong. 0x2002CCCF is used for signed nokia apps, while 0xA000D7CE is used for self signed apps, like my app is.

  4. #4
    Nokia Developer Moderator
    Join Date
    Sep 2004
    Location
    Tampere, Finland
    Posts
    11,359

    Re: DEPLOYMENT += makes installer_sis to fail

    DEPLOYMENT.installer_header sets the package UID for the Smart Installer wrapper package, the *_installer.pkg, and that UID must be 0x2002CCCF for Ovi Publish and Symbian Signed submissions.

    The problem is very likely in

    Code:
    vendorinfo = Matthieu
    my_deployment.pkg_prerules = vendorinfo
    What is Matthieu? A variable? A string? A vendor's name? Localized or not?

    The PKG file format requires the vendor name to be provided as
    Code:
    % {"CustomVendor-EN"}
    : "CustomVendor"
    therefore you have the corresponding qmake script
    Code:
    vendorinfo = \
    "%{\"CustomVendor-EN\"}" \
    ":\"CustomVendor\""
    
    my_deployment.pkg_prerules = vendorinfo
    DEPLOYMENT += my_deployment
    which after executing qmake, generates *.pkg files which contain the desired PKG content.

    If you want to generate

    Code:
    % {"Matthieu"}
    : "Matthieu"
    then your qmake script must contain

    Code:
    vendorinfo = \
    "%{\"Matthieu\"}" \
    ":\"Matthieu\""
    
    my_deployment.pkg_prerules = vendorinfo
    DEPLOYMENT += my_deployment
    How to verify if the scrip works? Run qmake after your *.pro edit and then inspect the *.pkg files, comparing them with known examples or analysing them using the documented PKG format specs.

    How to debug this type of errors?
    wcd_guide_installer.pkg(29) : error: unknown line
    Open the wcd_guide_installer.pkg file, go to line 29 and see what it contains vs what you expect it should contain. Then go to the *.pro file section which was supposed to generate the content of that line 29 and fix it. Easy.
    -- Lucian

    If you are not yet a DVLUP member it is time to correct that mistake :) Click here to join: http://www.dvlup.com/lucian/Invite

  5. #5
    Registered User
    Join Date
    Jan 2011
    Posts
    3

    Re: DEPLOYMENT += makes installer_sis to fail

    Lucian, thank you very much for your answer, you are right, obviously. I don't know what was in my head when I put a simple text as a vendor. Thanks also for the debug tips, they were very useful.

    Now I need a little more help, if you could spent 2 more minutes on my post. I have to submit the app urgently and I want to know if everything is ok. The app was rejected once and I don't have the time to wait to see if they will approve it this time. The reason of first rejection was:

    > ACTUAL RESULT: "Application not compatible with phone. Continue anyway?" error message is displayed.
    > EXPECTED RESULT: The application is downloaded and installed on the device without any issues. Any error or warning messages should not be displayed during installation.
    > AFFECTED DEVICES: All devices.
    > FREQUENCY REPRODUCED: 100%.


    In my .pro I have the next lines:

    # restrict supported platforms to those using
    # nHD resolution
    supported_platforms = \
    "; Supports S60 5th Ed and S^3" \
    "[0x1028315F],0,0,0,{\"S60ProductID\"}" \
    "[0x20022E6D],0,0,0,{\"S60ProductID\"}"

    default_deployment.pkg_prerules -= pkg_platform_dependencies
    deps.pkg_prerules = supported_platforms

    packageheader = "$${LITERAL_HASH}{\"WCD Guide\"}, ($${TARGET.UID3}), 1, 0, 0, TYPE=SA"
    deps.pkg_prerules += packageheader

    vendorinfo = \
    "%{\"Roche-Posay\"}" \
    ":\"Roche-Posay\""

    deps.pkg_prerules += vendorinfo

    DEPLOYMENT += deps


    In the initial submit, the last line wasn't there, cause it had causing me troubles.
    I want only to know if the app will be accepted this time. Thank you a million.

  6. #6
    Nokia Developer Moderator
    Join Date
    Sep 2004
    Location
    Tampere, Finland
    Posts
    11,359

    Re: DEPLOYMENT += makes installer_sis to fail

    The script looks good to me. As loong as those two platform dependencies are propagated to the PKG files and as long as you target for distribution only S60 5th Edition and Symbian^3 devices, you are fine with regards to this failure point.
    -- Lucian

    If you are not yet a DVLUP member it is time to correct that mistake :) Click here to join: http://www.dvlup.com/lucian/Invite

Similar Threads

  1. Carbide makes Eclipse unable to compile for x86/XP
    By robtow@tauzero.com in forum Carbide.c++ IDE and plug-ins (Closed)
    Replies: 1
    Last Post: 2008-06-12, 17:26
  2. PrintStream makes Bluetooth to disconnect?!
    By alegomes in forum Mobile Java Networking & Messaging & Security
    Replies: 1
    Last Post: 2006-10-15, 18:07
  3. @ character makes SyncML config fail in 6600
    By amunshi in forum General Messaging
    Replies: 0
    Last Post: 2005-06-02, 14:33
  4. Sending images and ringtones to different makes of phones.
    By tollervey in forum General Messaging
    Replies: 0
    Last Post: 2002-08-13, 08:27

Posting Permissions

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