How to modify the UID3 after creating a project?

[yfw1966]

hello everybody,

I created a new helloword project with carbide1.2 OEM.
Originally, It can be debugged on a device successfully, and It is signed only with the .cer and .key files which are created automatically at the time when built with gcce configuration.

Later, I modify the UID3 from 0xE25F9BA7 to 0xE25F9BA6 in the MMP file. at the same time I also modify other related file name. later it can pass building and run on the emulator. and also pass the building with a gcce configuration. After setting carefully the TRK option page in the debug dialog, I launch to debug, when, errors occur, It shows:
"
load failed
TRKPrltocolPlugin: Failed to launch the application(Either installing the application may have failed or dependented libraries may be missing)
"
Then I try it using the console command step by step. and It shows the error:
"encryption error, Can not read mykey,key"

I have no idea about this, I just modify the UID3.
Can anybody help me?

Thanks in advance!
Sophie

[kiran10182]

Search for old UID3 in your whole project and then replace all occurrence of it with newer UID. Then clean and Rebuild your application.

Kiran.

[yfw1966]

Thanks for your quick answer, but I made the same operation as you said before.
In addition, The error information shown in the console window is not correct. because I try anther project, the same error information is shown in the console window, but actually, the project can pass debugging on a device directly with carbide tools.

[kiran10182]

"
load failed
TRKPrltocolPlugin: Failed to launch the application(Either installing the application may have failed or dependented libraries may be missing)
"

I haven't encounter such a problem. But check this thread if it helps: http://discussion.forum.nokia.com/fo...d.php?t=113466

Kiran.

[yfw1966]

Maybe I do not have to modify UID3.
But my project is edited on the base of a sample in S60 sdk fp1. because it has dependence on a device ,I can only test it on a device, and there are some system capabilities included in my project, so I am planning to sign it with Open Signed Online.

But above of all, I have to modify the UID3 to make it different with the example's.
Can you tell me if there are other way to resolve it?

Thanks again.
Sophie

[wizard_hu_]

Unfortunately I do not really know the TRK plugin and on-device debugging, but it can happen that the project configuration 'remembers' your old UID, and when you debug, it tries to use it. You can either try to check every possible page in project properties, or simply delete the project from the workspace (make sure that your do not delete the files, so select the 'Do not delete contents'), then re-import the project from its bld.inf file.

[yfw1966]

yes, I forgot to update the project. I delete the project and upload it again as you said just now.
then when I launch the debugging again, the error is different and shown as follows:
"load failed
TRKProtocolPlugin: Unable to install the application, If self signing, certificate could be invalid if your PC clock is ahead of your phone clock. If now, your developer certificate may be invalid or UID of your application may be invalid or already in use."

Can anybody give me any advice to resolve it? or, Are there other ways to resolve it and do not have to modify the UID3?

Thanks and the best!
Sophie

[kiran10182]

...
TRKProtocolPlugin: Unable to install the application, If self signing, certificate could be invalid if your PC clock is ahead of your phone clock. If now, your developer certificate may be invalid or UID of your application may be invalid or already in use."

Can anybody give me any advice to resolve it?

Thanks and the best!
Sophie

So it has lot many reasons to say. Which of them suffice your problem? Just find it out.

Kiran.

[yfw1966]

During the R&D stage, the UID3 is limited to the scope of 0xE0000000 - 0xEFFFFFFF.
and when release with a PublisherID, is it still the same UID3? I think there possibly be a different UID3 for release Version. so I have to find a way to modify the UID3 after an application is created.

It is just my understanding, Can anybody give me any advice?

Thanks!
Sophie

[kiran10182]

Just read UID Faqs from Symbian signed for concrete answers.

https://www.symbiansigned.com/app/page/dev/uidfaq

Kiran.

[ltomuta]

There are at least two options:
1) Use a configuration file where you define the UIDs, say my_config.hrh

#ifndef __MY_CONFIG_HRH__
#define __MY_CONFIG_HRH__

#define __MY_FINAL_RELEASE_BUILD__ 0
#define __WILL_BE_CERTIFIED__ 0

#if __MY_FINAL_RELEASE_BUILD__
#if __WILL_BE_CERTIFIED__
// Symbian allocated value for Symbian Signed apps
#define KMyUidValue 0x2???????
#else
// Symbian allocated value for Self-Signed releases
#define KMyUidValue 0xA???????
#endif
#else
// R&D random value, not suitable for release
#define KMyUidValue 0xE???????
#endif

const TUid KMyAppUID3 = {KMyUidValue};

#endif

Then include the file and use the constants defined there wherever possible/suitable instead of the hardcoded values. When it comes to building the app for submission to Symbian Signed just modify the value of __MY_FINAL_RELEASE_BUILD__ and __WILL_BE_CERTIFIED__ accordingly and then re-build the application.

2) Use the plain hardcoded UID value as you see fit and as already used by the code generated by Carbide. When is time for a new release use a "replace in files" utility and replace all the occurrences of your old UID with the new value. Then re-build.

[yfw1966]

So it has lot many reasons to say. Which of them suffice your problem? Just find it out.

Kiran.

I can not find which clew is nicety. contrarily, I feel no error should occur in the process. because I just modify the UID3, and all files needed in the .pkg are all ready. and no more capabilities are added into the project. so, I think some problems is possibly related with the files of .cer and .key.
But I can not understand why I can not make use of the certificate which is created by the console command 'makekeys'.
ok, I will try applying anther certificate with the request tool.

[yfw1966]

Thanks to everybody,

now, I have proved that it was the problem of certificate which is related with the UID3. I will try to find a way to resolve it.

Thanks and the best!
Sophie

[yfw1966]

There are at least two options:
...

Thanks very much.