Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
02-01-2009 08:48 PM
I am having a hard time configuring my .jad file for OTA downloads. I am recieving the following error when I try to navigate to the jad file from the BlackBerry Browser.
"Error: Invalid manifest or application descriptor. The "MIDlet-Version" attribute is not a valid version number."
The contents of my jad file are as follows:
RIM-COD-SHA1-2: 91 64 64 84 7b 51 06 43 e6 f6 da 73 e3 43 fc b4 ed 4e 9a 1c
RIM-COD-SHA1-1: da d9 42 24 bd a5 fd 3f f6 a6 fe a4 6e 91 2f 3a 1a d7 e7 62
RIM-COD-SHA1: 64 b7 3b 1e 71 97 28 42 4d 36 0b 7e f6 94 2f 72 83 77 cb 99
I was having prior success with OTA but the version number was showing as 0.0 and the vendor "<unknown>". I believe this problem arose when I clicked "Title Resource Available" in the Resources tab of the project's properties. So far, no different value of version number that I have tried has proved successful. Anyone have any ideas? Thanks!
Solved! Go to Solution.
02-01-2009 11:30 PM
**Update: By creating a new project with a different name and regenerating the cod and jad files, I have been able to get OTA download working again. However, despite the fact that I set Version number and Vendor in the project properties neither of these values are making their way into the .jad file. Interestingly enough though, the text I entered into the 'Description' field does show up in the JDE autogenerated .jad file.
I am now hesitant to adjust the version number and vendor on the .jad file manually in case I end up in my original (much worse) situation of getting an 'invalid version number' error. Does anyone have any insight as to the cause of this behavior?
BTW, I'm compiling with version 188.8.131.52r of the JDE.
02-03-2009 06:36 AM
I had the same problem. The .jad file for a project does not seem to get automatically regenerated during a build so I have pre-build step defined in all my projects that deletes the .jad file, thereby causing it to be regenerated afresh each time. You can define a pre-build step on the Build tab of the project properties dialog. You'll want something along the lines of:
cmd.exe /C del com\company\product\AppName.jad
Note that the command executes with its working directory set to the location of the workspace file rather than the project file, i.e. you must specify the path to the .jad file relative to that.
04-22-2009 05:50 PM
Did you find out the source of the problem in the .jad file?
Having same problem and it did go away after I regenerated the .jad file.
But still wondering what the exact cause is?
09-30-2009 06:06 PM
Also having some issues getting my Hellow World WebIcon to be installed using OTA.
Everything compiles fine but I have following when browsing directly to .jad file
Error: Invalid manifest or application descriptor
The MIDlet version attribute is not a valid version number. Everything looks fine so I'm stuck as to how to proceed.
Any suggestions welcome.
09-30-2009 06:36 PM - edited 09-30-2009 06:36 PM
10-01-2009 02:52 PM