907 Errors when downloading an application
Here are some of the things that can cause a 907 error when downloading the application (as presented at DevCon)
Simple Issues
- The COD file is corrupt
- Rebuild (note that you will need to use a new version if this has already been pushed to the cloud)
- You didn't split your cod into siblings
- This is handled by our build tool but it can cause the problem if there is a single cod which is actually a zip of other cods.
- Someone is using a device from 2005. OS 4.0.0.171 through 4.0.0.215 had issues when the MIDlet-Jar-Size is not 0.
- Change it to 0 in the jad
- One of the COD files contains multiple periods
Server Related Issues
- 403 - Bad permissions on the COD files
- 404 - Can't find one of the CODs
- cods are in the wrong folder
- This can happen if a build was done manually and a cod wasn't uploaded.
- It can also happen if a customer is hosting and attempted a redirect or didn't put the cod and zips in the same directory.
- It may also indicate that a cod file hasn't been synced with the cloud.
- 406 - MIME Type not configured
- For .jad files: text/vnd.sun.j2me.app-descriptor
- For .cod files: application/vnd.rim.cod
Other Causes
- Attempting to upgrade via an OTA Download after an initial install was made by BES Push.
- Installing an application which attempts to change libraries used by other apps.
- Applications set to auto-run when an Exception is thrown on startup. This can be handled with a try/catch.
- Persistence Issues
- Recalling objects from persistence in a static context
- Timestamp mismatch - if a user downloads cod files from two separate builds the timestamp will not match. This error will sometimes not show itself until the device resets
- The application size is too large (support forums
).
