×

Discussion Board

Results 1 to 11 of 11
  1. #1
    Registered User
    Join Date
    Jul 2010
    Posts
    7

    Exclamation self-signed SIS pops "unable to install, component already built-in", using plugin

    Hello, buddies
    It is a open source project . I downloaded source code from online svn repo, and change the UIDs to test range. And made a self-signed SIS, but it pops "unable to install, component already built-in" while installing. It is using some plugins such like SyncML Client API plugin, SMS Utilities APIs, SW Installer Launcher APIs, Device Management Plugin APIs v.1.0. I downloaded all these plugins and make a success build but a bad installation.
    It blocked me for quite a few days, though I search it on internet but make no sense. If anybody give a hand, I would be quite grateful to him/her.
    Thanks
    Shawn

  2. #2
    Super Contributor
    Join Date
    Mar 2003
    Location
    Finland
    Posts
    9,553

    Re: self-signed SIS pops "unable to install, component already built-in", using plugi

    If you are including SIS(X) files in your own SIS file, remove them one by one, and repackage, resign and reinstall in between. When the error disappears, the last included/embedded SIS(X) file you removed was the culprit.

    Which SDK version are you using for the build?

    Which phone model are you trying to install on?

    What's in your .pkg file?

  3. #3
    Nokia Developer Moderator
    Join Date
    Feb 2006
    Location
    Oslo, Norway
    Posts
    28,674

    Re: self-signed SIS pops "unable to install, component already built-in", using plugi

    Changing the UID is not enough if you are experimenting with rebuilding a system-component, in that case you will also have to rename the installed files.
    Depending on what the application actually is, it might be enough to rename them in the .pkg file, and modifying the references in the .rss files (like app_file and perhaps localisable_resource_file in the _reg.rss, and icon_file in the main .rss).

  4. #4
    Registered User
    Join Date
    Jul 2010
    Posts
    7

    Re: self-signed SIS pops "unable to install, component already built-in", using plugi

    Hello, Petrib
    First, thanks a lot.
    I'm using S60_3rd_FP2_SDK_v1.1. I tried to install on S60_3rd_FP2_SDK_v1.1 emulator, and 5530xm (though 5530 is s60v5 based, it also is OK).
    It is an open source project.
    It includes main logic and four sub-parts:
    1. pushserver
    2. kickstarter
    3. uninstaller
    4. unit-test.
    All these four parts has own /data, /inc, /src, /sis folder.

    Main PKG file is as follow:
    ;----------------- Main PKG properties -----------------
    ;
    ;Languages supported: English(UK) and German.
    ;Will prompt a choice during installation, if the device langage is not one of these.
    &EN,GE

    ; standard SIS file header
    ; This name is displayed during installation, as the application name
    ; Add ",type=PU" for the partial update version
    #{"Funambol Sync","Funambol Sync"},(0xE001D2C7),8,5,0

    ;Localised Vendor name
    ; This name is displayed during installation, as the vendor name
    %{"Funambol","Funambol"}

    ;Unique Vendor name
    :"Funambol"


    ;Supports Series 60 v 3.0 (ALL S60-3)
    [0x101F7961], 0, 0, 0, {"Series60ProductID","Series60ProductID"}

    ;Supports Series 60 v 3.1 (S60-3 FP1), redundant
    ;[0x102032BE], 0, 0, 0, {"Series603rdFP1ProductID","Series603rdFP1ProductID"}

    ;Supports Series 60 v 3.2 (S60-3 FP2)
    ;[0x102752AE], 0, 0, 0, {"Series60ProductID","Series60ProductID"}
    ;Supports Series 60 v 5.0 (S60-5)
    [0x1028315F], 0, 0, 0, {"Series60ProductID","Series60ProductID"}
    ;Support N97 sdk
    [0x20014DDD], 0, 0, 0, {"Series60ProductID","Series60ProductID"}


    ;
    ;----------------- Files to install -----------------
    ;
    ;<source> <destination>

    ;JAM email client jad and jar files
    ;"FunambolEmailClient.jad" - "!:\Data\Installs\FunambolEmailClient.jad"
    ;"FunambolEmailClient.jar" - "!:\Data\Installs\FunambolEmailClient.jar"

    ; install push server
    "$(EPOCROOT)epoc32/release/gcce/urel/pushserver.exe" - "!:\sys\bin\pushserver.exe"

    {
    "$(EPOCROOT)epoc32/data/z/resource/apps/Funambol_0xE001D2C7.ren"
    "$(EPOCROOT)epoc32/data/z/resource/apps/Funambol_0xE001D2C7.rde"
    } -"!:\resource\apps\Funambol_0xE001D2C7.rsc"
    {
    "$(EPOCROOT)epoc32/data/z/private/10003a3f/apps/Funambol_0xE001D2C7_reg.ren"
    "$(EPOCROOT)epoc32/data/z/private/10003a3f/apps/Funambol_0xE001D2C7_reg.rde"
    } -"!:\private\10003a3f\import\apps\Funambol_0xE001D2C7_reg.rsc"

    ;for autostart
    {
    "$(EPOCROOT)epoc32/data/E001D2C7.ren"
    "$(EPOCROOT)epoc32/data/E001D2C7.rde"
    } -"!:\private\101f875a\import\[10003a3f].rsc"


    ; Here we copy the mandatory properties for upgrade (sw version...)
    "../sis/config/SyncClient/upgrade/config.ini" -"!:\private\10003a3f\Funambol\upgrade\config.ini"


    ; The application icon + svg images
    "$(EPOCROOT)epoc32/data/z/resource/apps/Funambol_0xE001D2C7.mif" -"!:\resource\apps\Funambol_0x10003a3f.mif"

    ; Contains the applications bmp used in About screen
    "$(EPOCROOT)epoc32/data/z/resource/apps/FunambolSync.mbm" -"!:\resource\apps\FunambolSync.mbm"

    ; Help file
    ;"../help/Funambol_0xE001D2C7.hlp" -"!:\resource\help\Funambol_0x10003a3f.hlp"

    ; Add any installation notes if applicable
    ;"readme.txt" -"!:\private\10003a3f\readme.txt"

    ;required for application to be covered by backup/restore facility
    "../sis/backup_registration.xml" -"!:\private\10003a3f\backup_registration.xml"

    "$(EPOCROOT)epoc32/release/gcce/urel/Funambol_0xE001D2C7.exe" -"!:\sys\bin\Funambol_0x10003a3f.exe"

    ; The uninstaller: will be launched while removing app (RR)
    ; Comment this line for a 'partial upgrade' pkg (PU)
    "$(EPOCROOT)epoc32/release/gcce/urel/FunambolUninstaller.exe" -"!:\sys\bin\FunambolUninstaller.exe",FR,RR,RW

    ; sync client kickstarter
    "$(EPOCROOT)epoc32/release/gcce/urel/kickstarter.exe" - "!:\sys\bin\kickstarter.exe",FR,RI



    **************************************** pushserver.pkg *********************************************
    ;Languages
    &EN
    ;

    ; Localised vendor
    %{"Funambol"}

    ; Non-localised vendor
    :"Funambol"

    ; Standard SIS file header
    #{"PushServer"},(0xE0026C70),1,0,0


    ;Supports Series 60 v 3.0
    [0x101F7961], 0, 0, 0, {"Series60ProductID"}
    ;Supports Series 60 v 3.1 (S60-3 FP1), redundant
    ;[0x102032BE], 0, 0, 0, {"Series603rdFP1ProductID"}

    ;Supports Series 60 v 3.2 (S60-3 FP2)
    ;[0x102752AE], 0, 0, 0, {"Series60ProductID"}
    ;Supports Series 60 v 5.0 (S60-5)
    [0x1028315F], 0, 0, 0, {"Series60ProductID"}


    ; Files to install
    ; uncoment this for autostart at device startup
    "$(EPOCROOT)epoc32\data\E0026C70.rsc" - "!:\private\101f875a\import\[E0026C70].rsc"
    "$(EPOCROOT)epoc32\release\GCCE\UREL\pushserver.exe" - "!:\sys\bin\pushserver.exe",FR,RI
    ; uncomment this for having application icon installed in Symbian default application directory
    "$(EPOCROOT)epoc32\data\z\private\10003a3f\import\apps\pushserver_reg.rsc" - "!:\private\10003a3f\import\apps\pushserver_reg.rsc"
    Last edited by wizard_hu_; 2010-09-07 at 17:39. Reason: hints

  5. #5
    Registered User
    Join Date
    Jul 2010
    Posts
    7

    Re: self-signed SIS pops "unable to install, component already built-in", using plugi

    Hello, Wizard_hu
    Thanks for your kind reply :-)
    It is an app to synchronize contacts information with remote server, using syncml protocol.
    I looked into the pkg files but didn't found file names which would conflict with systemp-component.
    It almost drove me crazy .
    Could you give me more advice or hints?
    Thanks for your kindness.
    Yours sincerely,
    Shawn

  6. #6
    Nokia Developer Moderator
    Join Date
    Feb 2006
    Location
    Oslo, Norway
    Posts
    28,674

    Re: self-signed SIS pops "unable to install, component already built-in", using plugi

    10003a3f is the UID of the menu application. It appears in the .pkg file because the registration resource file (a component of the icon) has to be deployed into its private folder, \private\10003a3f\import\apps - marked with blue in your post
    Every other usage of 10003a3f is wrong, revert them to E001D2C7. Marked with red (where applicable the "corresponding" E001D2C7 is also marked)

  7. #7
    Registered User
    Join Date
    Jul 2010
    Posts
    7

    Re: self-signed SIS pops "unable to install, component already built-in", using plugi

    Hi, Dear Wizard
    Thanks for your quick reply.
    I followed your instructions, and made a new build.
    The red marked three 10003a3f remained the same , all other occurrences were changed to E001D2C7. The error "unable to install, component already built-in" still exists.
    And I also tried to change the first two red marked to E001D2C7, keep the third , but build failed.
    Yours sincerely,
    Shawn



    ---------------------------------------------------------------
    ;----------------- Files to install -----------------
    ;
    ;<source> <destination>

    ;JAM email client jad and jar files
    ;"FunambolEmailClient.jad" - "!:\Data\Installs\FunambolEmailClient.jad"
    ;"FunambolEmailClient.jar" - "!:\Data\Installs\FunambolEmailClient.jar"

    ; install push server
    "$(EPOCROOT)epoc32/release/gcce/urel/pushserver.exe" - "!:\sys\bin\pushserver.exe"

    {
    "$(EPOCROOT)epoc32/data/z/resource/apps/Funambol_0xE001D2C7.ren"
    "$(EPOCROOT)epoc32/data/z/resource/apps/Funambol_0xE001D2C7.rde"
    } -"!:\resource\apps\Funambol_0xE001D2C7.rsc"
    {
    "$(EPOCROOT)epoc32/data/z/private/10003a3f/apps/Funambol_0xE001D2C7_reg.ren"
    "$(EPOCROOT)epoc32/data/z/private/10003a3f/apps/Funambol_0xE001D2C7_reg.rde"
    } -"!:\private\10003a3f\import\apps\Funambol_0xE001D2C7_reg.rsc"

    ;for autostart
    {
    "$(EPOCROOT)epoc32/data/E001D2C7.ren"
    "$(EPOCROOT)epoc32/data/E001D2C7.rde"
    } -"!:\private\101f875a\import\[E001D2C7].rsc"


    ; Here we copy the mandatory properties for upgrade (sw version...)
    "../sis/config/SyncClient/upgrade/config.ini" -"!:\private\E001D2C7\Funambol\upgrade\config.ini"


    ; The application icon + svg images
    "$(EPOCROOT)epoc32/data/z/resource/apps/Funambol_0xE001D2C7.mif" -"!:\resource\apps\Funambol_0xE001D2C7.mif"

    ; Contains the applications bmp used in About screen
    "$(EPOCROOT)epoc32/data/z/resource/apps/FunambolSync.mbm" -"!:\resource\apps\FunambolSync.mbm"

    ; Help file
    ;"../help/Funambol_0xE001D2C7.hlp" -"!:\resource\help\Funambol_0xE001D2C7.hlp"

    ; Add any installation notes if applicable
    ;"readme.txt" -"!:\private\E001D2C7\readme.txt"

    ;required for application to be covered by backup/restore facility
    "../sis/backup_registration.xml" -"!:\private\E001D2C7\backup_registration.xml"

    "$(EPOCROOT)epoc32/release/gcce/urel/Funambol_0xE001D2C7.exe" -"!:\sys\bin\Funambol_0xE001D2C7.exe"

    ; The uninstaller: will be launched while removing app (RR)
    ; Comment this line for a 'partial upgrade' pkg (PU)
    "$(EPOCROOT)epoc32/release/gcce/urel/FunambolUninstaller.exe" -"!:\sys\bin\FunambolUninstaller.exe",FR,RR,RW

    ; sync client kickstarter
    "$(EPOCROOT)epoc32/release/gcce/urel/kickstarter.exe" - "!:\sys\bin\kickstarter.exe",FR,RI

  8. #8
    Registered User
    Join Date
    Jul 2010
    Posts
    7

    Re: self-signed SIS pops "unable to install, component already built-in", using plugi

    Hi, wizard
    I'll try it again. Sorry for that I didn't see that you had already marked all places to revise .
    You are so kind :-)

    Sincerely
    Shawn

  9. #9
    Registered User
    Join Date
    Jul 2010
    Posts
    7

    Re: self-signed SIS pops "unable to install, component already built-in", using plugi

    Hi, wizard
    The built sis file which I built following your instruction, was successfully installed on actual device. Thanks for your kindness.
    But the app was killed right after the splash screen. Maybe I have some where else was not modified. Could you give me some hints?

    BR
    Shawn


    ******************** push server pkg ***************************************
    ; Standard SIS file header
    #{"PushServer"},(0xE0026C70),1,0,0


    ;Supports Series 60 v 3.0
    [0x101F7961], 0, 0, 0, {"Series60ProductID"}
    ;Supports Series 60 v 3.1 (S60-3 FP1), redundant
    ;[0x102032BE], 0, 0, 0, {"Series603rdFP1ProductID"}

    ;Supports Series 60 v 3.2 (S60-3 FP2)
    ;[0x102752AE], 0, 0, 0, {"Series60ProductID"}
    ;Supports Series 60 v 5.0 (S60-5)
    [0x1028315F], 0, 0, 0, {"Series60ProductID"}


    ; Files to install
    ; uncoment this for autostart at device startup
    "$(EPOCROOT)epoc32\data\E0026C70.rsc" - "!:\private\101f875a\import\[E0026C70].rsc"
    "$(EPOCROOT)epoc32\release\GCCE\UREL\pushserver.exe" - "!:\sys\bin\pushserver.exe",FR,RI
    ; uncomment this for having application icon installed in Symbian default application directory
    "$(EPOCROOT)epoc32\data\z\private\10003a3f\import\apps\pushserver_reg.rsc" - "!:\private\10003a3f\import\apps\pushserver_reg.rsc"

    ************************************* kickstarter pkg file *************************************
    ; Non-localised vendor
    :"Funambol"

    ; Standard SIS file header
    #{"KickStarter"},(0xE0026C71),1,0,0


    ;Supports Series 60 v 3.0
    [0x101F7961], 0, 0, 0, {"Series60ProductID"}
    ;Supports Series 60 v 3.1 (S60-3 FP1), redundant
    ;[0x102032BE], 0, 0, 0, {"Series603rdFP1ProductID"}

    ;Supports Series 60 v 3.2 (S60-3 FP2)
    ;[0x102752AE], 0, 0, 0, {"Series60ProductID"}
    ;Supports Series 60 v 5.0 (S60-5)
    [0x1028315F], 0, 0, 0, {"Series60ProductID"}


    ; Files to install
    "$(EPOCROOT)epoc32\release\GCCE\UREL\kickstarter.exe" - "!:\sys\bin\kickstarter.exe"
    ; uncomment this for having application icon installed in Symbian default application directory
    "$(EPOCROOT)epoc32\data\z\private\10003a3f\import\apps\kickstarter_reg.rsc" - "!:\private\10003a3f\import\apps\kickstarter_reg.rsc"


    ************************************* Unit test pkg **************************************

    ;Language - standard language definitions
    &EN

    ; standard SIS file header
    #{"FunambolClientUTest"},(0xEEBB239C),8,0,0

    ; List of localised vendor names
    %{"Funambol"}

    ;Unique Vendor name
    :"Funambol"

    ;Supports Series 60 v 3.0
    [0x101F7961], 0, 0, 0, {"Series60ProductID"}

    ;Files to install
    ;You should change the source paths to match that of your environment
    ;<source> <destination>
    "$(EPOCROOT)epoc32\release\GCCE\UREL\client_unit_test_0xEEBB239C.exe" -"!:\sys\bin\client_unit_test_0xEEBB239C.exe"
    "$(EPOCROOT)epoc32\data\z\resource\apps\client_unit_test_0xEEBB239C.rsc" -"!:\resource\apps\client_unit_test_0xEEBB239C.rsc"
    "$(EPOCROOT)epoc32\data\z\private\10003a3f\apps\client_unit_test_0xEEBB239C_reg.rsc" -"!:\private\10003a3f\import\apps\client_unit_test_0xEEBB239C_reg.rsc"
    "$(EPOCROOT)epoc32\data\z\resource\apps\client_unit_test_0xEEBB239C.mif" -"!:\resource\apps\client_unit_test_0xEEBB239C.mif"
    "..\help\client_unit_test_0xEEBB239C.hlp" -"!:\resource\help\client_unit_test_0xEEBB239C.hlp"


    ;Testcases input files
    ;"..\..\cpp-sdk\test\testcases\ex1.xml" -"!:\private\EEBB239C\ex1.xml"


    ; Add any installation notes if applicable
    ;"client_unit_test.txt" -"!:\private\EEBB239C\client_unit_test.txt"

    ;required for application to be covered by backup/restore facility
    "backup_registration.xml" -"!:\private\EEBB239C\backup_registration.xml"


    And the main PKG file in former posts.

  10. #10
    Nokia Developer Moderator
    Join Date
    Feb 2006
    Location
    Oslo, Norway
    Posts
    28,674

    Re: self-signed SIS pops "unable to install, component already built-in", using plugi

    If it starts, the installation succeeded (to some extent). You could enable the error messages on the device (http://wiki.forum.nokia.com/index.ph...fication_codes), but after that the debugging part is going to happen. Configure "On-Device Connections..." (Help menu of Carbide.c++) and start experimenting. Though a bit outdated, you can get some ideas from http://wiki.forum.nokia.com/index.ph...arbide.c%2B%2B

  11. #11
    Registered User
    Join Date
    Jul 2010
    Posts
    7

    Re: self-signed SIS pops "unable to install, component already built-in", using plugi

    Thanks, wizard
    I found the solution because I used a wrong API plugin.
    I am very grateful for your help.
    Wish you happy every day :-)

    BR
    Shawn

Similar Threads

  1. [Moved] "Unable to install. Component is built in." on N86 8mp nokia phone
    By chandran.biju007 in forum Symbian Signed Support, Application Packaging and Distribution and Security
    Replies: 3
    Last Post: 2010-03-22, 16:45
  2. Replies: 8
    Last Post: 2010-02-28, 18:30
  3. [moved] "unable to install. component is already built in" message on emulator.
    By Rajani_sp in forum Symbian Signed Support, Application Packaging and Distribution and Security
    Replies: 22
    Last Post: 2008-08-19, 16:31
  4. Self-signed application error :"Unable to install. Component is built-in"
    By hoangtv1 in forum Symbian Signed Support, Application Packaging and Distribution and Security
    Replies: 6
    Last Post: 2008-04-12, 21:47
  5. Replies: 8
    Last Post: 2006-02-16, 06:10

Posting Permissions

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