Errors occured in signed midlet:
Invalid Application : This might happen due to MIDlet-Permissions attribute. Check all the attributes are there for which permission is required. Mostly comes in S40 handsets of the application is signed.
Root certificate missing from phone: The Java Verified certificate and/or Verisign certificates are missing from some phones check under Tools->Settings->Certificate Management for the relevant certificate
Authorization Failed: There are a whole host of possible reasons behind this here are the ones I’ve come across
1.Certificate missing from phone, double check your certificate is installed and has been marked as trusted for application installs in Certificate Management
2.Reboot: Uninstall the application completely then reboot your phone try taking the battery and SIM out too, often things get themselves in a twist, especially if you’ve been re-installing a lot without uninstalling first
3.JAD/JAR mismatch: Double check the application size in the JAD, remember it’s the number of bytes that is important NOT the size on disk
4.Browser cache: If you’re installing over the air make sure you clear your browser cache before installing
5.I’ve heard but not verified that line breaks in the MIDlet-Permissions can cause problems but it seems ok to me on Nokia 6680/6630/6230i (could be firmware dependent?)
6.The MIDlet-Permissions attribute is the cause of a lot of problems (especially since the documentation is often wrong/missing or different depending on the phone), try leaving it out first and add permissions in one at a time. Some phones will complain about permissions they don’t support, some will ignore them
Authentication Failure : This may occur in the signed build due to date conflict of handset with that of the signed certificate apart from the other reasons mentioned in above in authorization failed section. Please make sure your handset date time is correct.