My application must send itself to other mobiles via blooth on s60 3rd platform.
Does symbian provides anyways to backup sis file when it is being installed.
if not, can application intalled make the same signed sis file on mobile?
Re: How to backup the sis file when it is being installed,or is
You can't easily rebuild a SIS file on any Symbian 9 based device (because the file must be signed).
You must yourself work out a way to keep a second copy of a signed SIS package to send (the device/OS will not do it for you). In addition, you need to work around the built-in "Closed Content List" that makes it more difficult to send/forward certain file types (such as .sis/.sisx, .jar, etc.).
Re: How to backup the sis file when it is being installed,or is
The "Closed Content List" is there just prevent the phone from sending/forwarding files of a specific type. There's no built-in support/mechanisms that allow you to keep a second copy of a signed SIS package (except including/embedding it yourself in another "wrapper" SIS package and then taking care of it yourself in your own code).
Perhaps, if you need to send your app to some other user, just keep it on the web and have your app send a link to it? That'd be the easiest way, IMO.
Re: How to backup the sis file when it is being installed,or is
Having a signed sis file wrapped in another sis file will only enable the phone with the original wrapper sis file to spread the packaged sis file around, unless it is wrapped again and again to infinity.
If the application doesn't need to be Symbian signed you can create the sis file on the phone and self sign it. You will need to write a program to make a sis file and sign it, check out format of sis files softwareinstallsis.pdf. I have not read through this.
As for "Closed Content List" I don't know, you would probably need to have capabilities to get past it, which means this method will not work. What do you think N_A?
Another thought just occurred to me, why does Symbian require self signing? Anyone can do it, so there is no security gain. It only consumes time when creating the sis file and when installing the sis file.(I guess 6 sec is not too much) Am I missing something?
Forum posts: 720
You can't easily rebuild a SIS file on any Symbian 9 based device (because the file must be signed).
You must yourself work out a way to keep a second copy of a signed SIS package to send (the device/OS will not do it for you). In addition, you need to work around the built-in "Closed Content List" that makes it more difficult to send/forward certain file types (such as .sis/.sisx, .jar, etc.).
Forum posts: 8
Thanks for your answer, can you tell me how to keep a second copy of a signed SIS package? can "Closed Content List" do this?
Forum posts: 720
The "Closed Content List" is there just prevent the phone from sending/forwarding files of a specific type. There's no built-in support/mechanisms that allow you to keep a second copy of a signed SIS package (except including/embedding it yourself in another "wrapper" SIS package and then taking care of it yourself in your own code).
Perhaps, if you need to send your app to some other user, just keep it on the web and have your app send a link to it? That'd be the easiest way, IMO.
Forum posts: 68
Having a signed sis file wrapped in another sis file will only enable the phone with the original wrapper sis file to spread the packaged sis file around, unless it is wrapped again and again to infinity.
If the application doesn't need to be Symbian signed you can create the sis file on the phone and self sign it. You will need to write a program to make a sis file and sign it, check out format of sis files softwareinstallsis.pdf. I have not read through this.
As for "Closed Content List" I don't know, you would probably need to have capabilities to get past it, which means this method will not work. What do you think N_A?
Another thought just occurred to me, why does Symbian require self signing? Anyone can do it, so there is no security gain. It only consumes time when creating the sis file and when installing the sis file.(I guess 6 sec is not too much) Am I missing something?