Installation of MIDlet failes on Nokia 6600 Invalid Manifest

[lancew]

Hello All,
I have developed a MIDlet for my company that currently runs on Motorola phones. They want it to be able to port to non-Motorola phones, and the first one they got me is the Nokia 6600.

When installing the app using the PC Suite For Nokia 6600 application, and an IR link, the entire JAR file seems to get transferred, and then I get an "Invalid Manifest" error.

I am using jBuilder X to create the Jad, and Jar files.

If anyone has a solution, I would really appreciate it.

Lance

[lancew]

Hello again.
I have a little additional info. I have redone all my paths, and removed all the spaces. I used jBuilderX to create the JAD, and JAR Files.

In the Emulator (Series_60_MIDP_SDK_2_1_Beta) I see the following warning:
WARNING: JAD file and JAR manifest have differing values for attribute MIDlet-1
The midlet then starts normally in the emulator.

I checked the Manifest File in the JAR, and the MIDLet-1 Line has been wrapped with a \n followed by a space. I manually edited the file, but it still comes up with the same "Invalid Manifest" when installing to the actual phone.

If anyone has any ideas as to the problem, I would be very appreciative!

Thanks
Lance

[lancew]

Am I the only one to ever have experienced this? Is there any Nokia Documentation on the manifest files, and the correct structure of them?


Thanks
Lance

[enough]

Hi lancew,

you could try J2ME Polish for building the appropriate JAR and JADs. Since it is based on Ant, it integrates nicely with JBuilder. Also it does not wrap any class-names within the manifest.

http://www.j2mepolish.org
http://www.j2mepolish.org/docs/install.html#jbuilder

Best regards,
Robert

[sb101]

Lance, did you ever get a solution to this? I have the exact same problem.

[lancew]

I did find a solution. It was the version number I was using. I had it set to 1.1e because that is what the application that runs on the PC, and does the same thing is versioned at. I changed it to 1.1 and that did the trick.

I don't know if this is the same situation as yours, but that's what did it for me.

If not, check all the values in the JAD, including file size.

[Donz]

According to specification, attributes MIDlet-Name, MIDlet-Vendor, MIDlet-Version must be the same in jad and manifest.
To make sure I make value of attribute MIDlet-1 the same too.