MIDlet signed with 4.3 tools is not signed on 4.1 OS?
 

Hey all, I'm new to development on the blackberry platform, and probably like many people I'm having trouble trying to sign my first application. I believe, though I haven't been able to confirm, that my issue is as follows:
* I generated my keypairs using the 4.3 jde components. I did this before I realized that:
* My blackberry is running the 4.1 version of the OS

I am able to compile my cod file (using the 4.1 jde components, which I downloaded after many hours of distress at this mysterious 907 invalid cod message I got when trying to install my 4.3 compiled cod), and install it OTA to my blackberry (with the unsigned warning) and executes fine. I'm able to sign my cod (the status shows as 'Signed' in the Signature Tool, and the cod file size changed, though the jad attributes for the cod size and sha1 were unchanged; and updating these attributes had no effect on my problem). However, when I go to install my spiffy newly signed midlet, I get the same unsigned warning message, though it still installs and executes so whatever the signing is doing it's not hurting anything. Any thoughts would be greatly appreciated; could this be due to generating my keypairs originally with the 4.3 tools, and therefore signing with the 4.3 tools, but trying to run the signed midlet on my 4.1 blackberry? Thanks!

You can use the JDE 4.3 to develop 4.1 applications, just don't call anything in the API that was added after 4.1. The API docs say what version stuff was added at.

Right, I'm not using any blackberry-specific API methods at all in fact. I'm just trying to sign the code to get rid of all the warning messages, and hopefully allow midlets launched by the PushRegistery.registerAlarm to run without prompting the user for permission. However, the the cod file that the 4.3 tool builds won't install on my 4.1 blackberry (907 Invalid COD). And with my keypairs which I generated with the 4.3 tools I can sign my cod file (double-clicking it confirms the signature in the Signature Tool), but when I install the midlet on my phone it gives me the usual 'unsigned midlet' warning.

Which is what leads me to believe that I may need to purchase a new set of keys and generate keypairs using the 4.1 tools so I can sign with them.

solution
 

Ok, in case anyone else runs into this issue, two things going on here:

1. Blackberry 4.1 phones always display the warning 'This application does not contain a signature. It might not be from a trusted source. Do you want to proceed?' when installing OTA: Knowledge Center - This application does not contain a signature

2. When signing 4.1 applications it is best to use the 4.3 tools (since you get the nice '-p passphrase' option for the SignatureTool.jar), however, if you do so, don't forget to copy the sigtool.bat, sigtool.csk, sigtool.db and the SignatureTool.jar from the 4.3 bin to the 4.1 bin. Reference: Knowledge Center - Signature Key format changes in BlackBerry JDE 4.3.0