Installation of a signed midlet fails
Article Metadata
If you are not able to install a midlet that is Java Verified, check the following:
- UTI root certificate is in the device.
- For example: Tools -> Settings -> Security -> Certif. management: MIDP2 Geotrust CA for UTI (This path is device dependent)
- In case you have signed your MIDlet with some other certificate, the corresponding root certificate has to be in the device. Possible certificates are available from Thawte and Verisign. It is generally not possible to use certificates created on your own, or Symbian Developer certificates for MIDlet signing.
- The application is signed only once.
- If there are other signatures than the Java Verified, then that could be an issue. There can only be one signature (one MIDlet-Certificate-1-1 and one MIDlet-Jar-RSA-SHA1).
- The date and time are correct in the device.
- JAR manifest file matches with JAD MIDlet-fields (even a minor mismatch can fail the installation).
- The MIDlet-permission fields are correct and supported by the target device.
- The SIM card is present in the device.
19 Sep
2009
This simple article highlights several simple, but common problems that may lead to problems installing a signed Java ME midlet. Midlet signing can be very confusing for beginners, and the reason for the errors can often be difficult to track down. Almost every day, new threads are to be found in the discussion forums relating to problems installing signed Midlets. Some of the most common and confusing problems relate to a failure to list the required API permissions in the JAD file. Renaming a Midlet (and resulting inconsistency between the Midlet name and what appears in the JAD file) is another common cause of troubles.
The following link provides a useful discussion of midlet signing and common problems encountered: Midlet signing