Archived:Pkg must not contain files that are modified during run time (Known Issue)

Comments

(no comments yet)

Log in or Join to leave comments.

Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

Article Metadata

---

Compatibility

Platform(s): S60 3rd Edition

---

Article

Created: User:Technical writer 1 (20 Aug 2007)

Last edited: hamishwillee (21 Jun 2012)

Overview

If an application can be installed to a removable storage (memory card), make sure that the .pkg file used to create the .sis package doesn't list any files that are modified during run time. This applies to both standard application (SIS type SA) and preinstalled application (SIS type PA) packages.

If any of the files listed in .pkg (e.g. a configuration file) are modified, propagation will fail when the memory card is inserted in another device or when the phone memory (C drive) is formatted. This happens because the modified file(s) no longer match the checksum created during the initial installation, and the installer assumes they have been tampered with.

Solution

One possible solution to this problem is that when updating a (e.g. configuration) file, the application will treat the original file as read-only. Any changes will be stored to a copy of the original.