Archived:MIDlet attributes on JAD and manifest files must match (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}}.

The article is believed to be still valid for the original topic scope.

Article Metadata

---

Compatibility

Platform(s): S60 3rd Edition

---

Article

Created: User:Technical writer 1 (19 Dec 2006)

Last edited: hamishwillee (28 Jun 2012)

Overview

when installing a signed MIDlet on an S60 3rd Edition device, the installation fails with an error stating that the JAD and manifest attributes do not match if there are extra spaces around the MIDlet-<n> attributes in one of the files and no extra spaces in the other file;

Description

The MIDP specification states that: "If the MIDlet suite is trusted then the values in the application descriptor MUST be identical to the corresponding attribute values in the Manifest."

It also states about JAD and manifest attributes: "Leading and trailing spaces in name, icon and class are ignored."

However, when installing a signed MIDlet on an S60 3rd Edition device, the installation fails with an error stating that the JAD and manifest attributes do not match if there are extra spaces around the MIDlet-<n> attributes in one of the files and no extra spaces in the other file. For example, if the MIDlet is signed and if the manifest file contains the following entry (note that there is one extra space character after the colon):

MIDlet-1: ;HelloWorld, , com.nokia.fn.HelloWorld

and the JAD file contains the following entry:

MIDlet-1: HelloWorld, , com.nokia.fn.HelloWorld

The installation will fail.

Solution

The workaround is to make sure that the manifest and JAD attributes match exactly and that there are no extra spaces.