Archived:Installation of PA-type SIS may fail if user interaction is required (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}}.

Propagation of preinstalled (SIS type PA) packages may fail on S60 3rd Edition if the pkg file contains certain options that would require user interaction during installation.

Article Metadata

---

Compatibility

Platform(s): S60 3rd Edition

---

Article

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

Last edited: hamishwillee (21 Jun 2012)

Description

The installation of a PA-type SIS is meant to be an automatic process that does not require user interaction. For example, text dialogs (pkg option FILETEXT) are ignored for preinstalled packages. However, problems may arise when the pkg supports multiple languages and contains language-dependent files - specifying a list of files, of which only one will be installed, depending on the language selected by the user during installation:

{"source-filename1", "source-filename2", ...} - "destination-filename"[, install-options]

If the current language setting of the device does not match to any language specified in the SIS, the user is asked to select a language from a list. This fails for PA-type packages.

Solution

Use only language-independent files for preinstalled packages. For packages supporting multiple languages, install resource files for all the languages - this way no user interaction is required and the silent installation will work. Another advantage is that if the user subsequently changes the language setting of the device, the installed application will also change its language (assuming it is localized for the new language).