[moved] Problems during the installation of a new version.

[NikolaN]

The new version doesn’t want to update an old one and shows a message: «Update error». At that the problem cannot be solved even if we delete the whole body from PKG file and the title take from PKG file of the previous version. But it’s possible to install the old version over the installed new version. Also it’s possible to install the new version after the deletion of the old one.
1. The certificates in both versions are similar.
2. The old version includes two inserted SIS files. The new version doesn’t include inserted SIS files.

Please, help me to solve the problem.

[symbianyucca]

you could try commenting out the pkg lines one-by-one, untill you can isolate the actual line that causes the problem

[NikolaN]

I commited whole PKG (in PKG left only header, and header I changed many times).
And I can not modify anythig in old PKG file.

[wizard_hu_]

2. The old version includes two inserted SIS files. The new version doesn’t include inserted SIS files.

If it means that you have moved files from the embedded .sisx-es to your main package, that causes the update error. The files on the device are considered to belong to the embedded .sisx files, and not to your main package.

[NikolaN]

If it means that you have moved files from the embedded .sisx-es to your main package, that causes the update error. The files on the device are considered to belong to the embedded .sisx files, and not to your main package.

Yes. You are right. But how can I fix it? (Of course I do not want to move back SIS files, and In fact do not want to create EXE fole for uninstall old version)

[symbianyucca]

then you would need to rename the files that were on the embedded sis, as well as change any UIDs with them. Or instruct your users to uninstall the application before installing the new version..

[NikolaN]

In this way, one more question. Why do not installing new version whis PKG file like this:

;Languages
&EN

;Header
#{"Temp"},(0x0000123),*VERSIONNUMBER*,TYPE=SA

;Localised Vendor name
%{"My company"}

;Unique Vendor name
:"My company Inc"

;Supports Series 60 v 5.0
[0x1028315F], 0, 0, 0, {"Series60ProductID"}

over old cersion? (any files for conflict whith old version)

[symbianyucca]

Not sure what you mean, so can you explain in bit more details on what happens and whet are you trying to do ?

[NikolaN]

Ok. Lets begin
Old PKG file lock like:
;Languages
&EN
;Header
#{"App "},(0x00001234),*VERSIONNUMBER*,TYPE=SA
;Localised Vendor name
%{"Vendor"}
;Unique Vendor name
:"vendor Inc"
;Supports Series 60 v 5.0
[0x1028315F], 0, 0, 0, {"Series60ProductID"}

@"*EPOCROOT*epoc32\SISFILES\first.sis",(0x12345678)
@"*EPOCROOT*epoc32\SISFILES\second.sis",(0x12345679)

... other included fies

new PKG file lock like:
;Languages
&EN
;Header
#{"App "},(0x00001234),*VERSIONNUMBER*,TYPE=SA
;Localised Vendor name
%{"Vendor"}
;Unique Vendor name
:"vendor Inc"
;Supports Series 60 v 5.0
[0x1028315F], 0, 0, 0, {"Series60ProductID"}

=> do not contain any file.
New version can not installing over old. But old can install over new.

[symbianyucca]

ok, I propably have not see that earlier, but if you verify that it works like that, then it appears that the update error can also be coming from situations like that, though I can not see the logic on why it would behave like that..

[NikolaN]

I found something intresting. If I deleted inserted SIS files from old version everising nice.