SIS file error, test.sis is not a SIS file.

[jobincantony]

hi,

I am developing an application for S60 2nd edition devices.

I am able to build the application and installed it in devices.

It works pretty good.

The problem is when i am trying to sign my application using developer certificate, it shows an error

1) In one machine it shows..

"SIS file error, test.sis is not a SIS file."
(i typed signsis test.sis testsigned.sis test.cer test.key)

2) In another machine i got the error

"Sorry, \epoc32\tools\signsis.exe is not supported in this release. Please use a different device."

My default device is S60_2nd_fp2_cw.

Please help me to solve the issue..

Thanks in advance,

Jobin

[petrib]

You don't sign S60 2nd Ed. .sis files yourself. They don't need to be signed, but they can be signed through Symbian Signed.

S60 3rd Ed. .sis files must be signed (self signed or Symbian Signed depending...), and then they should be renamed .sisx to make it clear to users and web servers that it is a file intended for Symbian 9/S60 3rd Ed. devices, and not earlier versions.

[ltomuta]

One small correction: S60 2nd Edition sis files can also be [self-]signed, the certfificates are however declared in the *.pkg file and the only tool to be called is makesis.

[jobincantony]

Hi,

Thanks for the response.

my certificate file : test.cer
key file : test.key
password : test123

i added below line in my .pkg file

*"test.key","test.cer",KEY="test123"

After that i run makesis myapp.pkg

but it shows an error
"error: incorrect password, check your password"
"error: cannot open file, check filename and access rights".


But i am able to sign 3rd edition using the same files and password.

Could anyone plz help me to solve this issue...

jobin

[wizard_hu_]

I can not reproduce your problem.

The .pkg file is

#{"TesTes"},(0x01644A93),1,0,0

*"Test.key","Test.cert",KEY="test123"

; Series 60 v 0.9
(0x101F6F88), 0, 0, 0, {"Series60ProductID"}
"C:\Symbian\8.0a\S60_2nd_FP2_CW\Epoc32\release\armi\urel\TesTes.app"-"!:\System\Apps\TesTes\TesTes.app"
"C:\Symbian\8.0a\S60_2nd_FP2_CW\Epoc32\data\z\system\apps\TesTes\TesTes.rsc"-"!:\System\Apps\TesTes\TesTes.rsc"

and I have tried to create the certificate files with
- makekeys -cert -dname "CN=Wizard OU=AUT" Test.key Test.cert, and answering "y", then typing password
- makekeys -cert -password test123 -dname "CN=Wizard OU=AUT" Test.key Test.cert
- makekeys -cert -password "test123" -dname "CN=Wizard OU=AUT" Test.key Test.cert
All three works well. Changing to 3rd MR (obviously fails) fails with other with different error message.

Check if the example in Examples\toolsandutilities\install (helloworldsecure.pkg) with your configuration.

[kiran10182]

Hello Jobin,

hi,

I am developing an application for S60 2nd edition devices.

I am able to build the application and installed it in devices.

It works pretty good.

The problem is when i am trying to sign my application using developer certificate, it shows an error

1) In one machine it shows..

"SIS file error, test.sis is not a SIS file."
(i typed signsis test.sis testsigned.sis test.cer test.key)

2) In another machine i got the error

"Sorry, \epoc32\tools\signsis.exe is not supported in this release. Please use a different device."

My default device is S60_2nd_fp2_cw.

Please help me to solve the issue..

Thanks in advance,

Jobin

Would you please list down entries of your .pkg file here?

Kiran.

[jobincantony]

Hi,

This is my .pkg file

; Test.pkg

;Language - standard language definitions
&EN

; standard SIS header
#{"Test"},(0x20017165),2,0,6

;Localised Vendor name
%{"Vendor -EN"}

;Unique Vendor name
:"Vendor"

;Supports Series 60 v 2.0
(0x10200BAB), 0, 0, 0, {"Series60ProductID"}

;Signing files
*"Test.key","Test.cer",KEY="test123"

;Files to install
"C:\Symbian\8.0a\S60_2nd_FP2_CW\epoc32\release\thumb\urel\TestV20.app" -"!:\system\apps\TestV20\TestV20.app"
"C:\Symbian\8.0a\S60_2nd_FP2_CW\epoc32\data\z\system\apps\TestV20\TestV20.rsc" -"!:\system\apps\TestV20\TestV20.rsc"
"C:\Symbian\8.0a\S60_2nd_FP2_CW\epoc32\data\z\system\apps\TestV20\TestV20.aif" -"!:\system\apps\TestV20\TestV20.aif"
"C:\Symbian\8.0a\S60_2nd_FP2_CW\epoc32\data\z\system\apps\TestV20\TestV20_caption.rSC" -"!:\system\apps\TestV20\TestV20_caption.rSC"
"C:\Symbian\8.0a\S60_2nd_FP2_CW\Epoc32\release\thumb\urel\TestSdkSymbian.dll" -"C:\system\libs\TestSdkSymbian.dll"

; Files to remove on uninstallation

""-"!:\System\Apps\TestV20\TestV20.ini",FN.

I can also sign using the .cer and .key file generated by the wizardbut it wil not solve my issue...

If we sign using the wizard generated files a warning message popup at the time of installation

" Unable to verify Supplier. Continue Anyway?".

i need to resolve that issue.

I have a publisherID and i was able to sign the 3rd edition using this publisherID. I purchased the publisherID recently.
I think the new publisherID may not support older symbian versions..

[Symbian_Neil]

If we sign using the wizard generated files a warning message popup at the time of installation

" Unable to verify Supplier. Continue Anyway?".

i need to resolve that issue.

Well AFAIK, this warning will go away only after you sign through Symbian Signed. For self signed, you cannot avoid this warning.

[jobincantony]

Well AFAIK, this warning will go away only after you sign through Symbian Signed. For self signed, you cannot avoid this warning.

Neil,

Well.. i know that ..

The question is how can i sign the second edition using my TC trustcenter PublisherID ??

[hardbond]

1. Locate your .pfx file from TCT
2. Locate the tcp12p8.bat tool provided on http://developer.symbian.com/wiki/di...n+Signed+Tools
3. Edit the tcp12p8.bat file and remove/comment out the line if EXIST %keyFileTmp% del %keyFileTmp%
4. Run tcp12p8.bat on the .pfx file
5. This will produce a file <something>.key.ossl
6. Rename this .ossl file to a .key file and use this file to sign pre v9 files instead of the original .key file
7. In the result .ossl (or now named .key file), delete all the text that precedes the -----BEGIN RSA PRIVATE KEY-----
8. Make a copy of your .cer file, and do the same here - delete all the text that precedes the -----BEGIN CERTIFICATE-----

Hardy Thomas

[jobincantony]

Thank you hardy,

I successfully ExpressSigned my application .

Instead of deleting the text precedes the ----Begin Private Key ---- and ----Begin Certficate---- in step 7 and 8, i just cut the text from there and paste it after ---End Private key---- and ---End Certificate---..

regards,

jobin