This is some info that I have collected from several sites over the years (as well as a large dose of personal experience) concerning MIDP Errors – maybe it will help others.

Code Description Possible Explanation
900 Success
901 Insufficient Memory If there is insufficient memory to store the MIDlet suite on the device, the device MUST return Status Code 901
902 User Cancelled
903 Loss of Service If the network service is lost during installation, Status Code 903 SHOULD be used in a Status Report if possible (it may be impossible to deliver the status report due to the network-service outage).
904 JAR size mismatch If the received JAR file size does not match the size specified in the Application Descriptor, the device MUST return Status Code 904
905 Attribute Mismatch If the mandatory attributes in the descriptor “MIDlet-Name”, “MIDlet-Version”, and “MIDlet-Vendor” do not match those in the JAR manifest, the device MUST return Status Code 905
905 Attribute Mismatch If the MIDlet suite is trusted, then the values in the application descriptor for all MIDlet-* attributes MUST be identical to the corresponding attribute values in the Manifest. If not, the device MUST return Status Code 905
906 Invalid Descriptor If the device receives a URL (for MIDlet-Install-Notify or MIDlet-Delete-Notify) longer than 256 UTF-8 encoded characters it MUST reject the installation and return Status Code 906
906 Invalid Descriptor The attributes in the descriptor MUST be formatted according to the syntax in the MIDP specification and all of the attributes required by the MIDP specification MUST be present in the descriptor. If this is not the case, then the client MUST return Status Code 906
906 Invalid Descriptor Manifest is too big or does not exist in JAR
906 Invalid Descriptor Indicates that the device could not interpret the Download Descriptor. This typically means a syntactic error.
907 Invalid JAR If the JAR is not available at the MIDlet-Jar-URL attribute in the descriptor, the device MUST return Status Code 907.
907 Invalid JAR If the JAR manifest is not in the correct syntax, or if any of the required attributes are missing in the JAR manifest, the device MUST return Status Code 907
908 Incompatible Configuration or Profile
909 Application authentication failure If the application failed to be authenticated, the device MUST return Status Code 909
910 Application authorization failure If the application is an unsigned version of an installed signed version of the same application, the device MUST return Status Code 910
910 Application authorization failure If the application is not authorized for a permission listed in the MIDlet-Permissions attribute, the device MUST return Status Code 910
910 Application authorization failure Make sure that an unsigned version is not already installed. You cannot install a signed app over an unsigned one, so delete the earlier version.
911 Push registration failure If a static push registration fails for a reason other than not being authorized, the device MUST return Status Code 911
912 Deletion Notification In the case of a deletion status report, the notification is sent only when the MIDlet is deleted; Status Code 912 MUST be sent, notifying that the deletion occurred. Editor’s Note: Unless, of course, you are Sprint, then you send it the next time an app is installed from that site – doh!)

Other Considerations:

  • MIDlet-Version – Maximum 2 digits per number: 1.99.23 okay, 1.0.100 is wrong
Share and Enjoy:
  • Digg
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • Twitter