Unable to install j2me apps in my Nokia N95 8GB (North America)

Hi,

I recently purchased a Nokia N95 8GB NA version from Dell. Unfortunately my Verisign signed midlet can not be installed in my brand new N95-4. The same signed midlet works perfectly in an unlocked NOkia N73.

With my N95-4, installing the signed midlet results in an error "Certificate Error: Contact the application provider".

I have followed some recommendations about disabling certificate checks, but that did not help resolve the problem.

Here is the list of certificates I can see currently installed in my brand new N95-4:

1. Baltimore CyberTrust Mobile Root
2. Baltimore CyberTrust Root
3. Entrust.net Secure Server Certification Authority(2)
4. Entrust.net Secure Server Certigication Authority (2048)
5. Entrust.net SEcure Server Certification Authority
6. Equifax secure Certificate Authority
7. Equifax Secure Global eBusiness CA-1
8. GlobalSign Certificate Authority
9. GlobalSign Root CA
10. GoDaddy Class 2
11. GTE Cyber Trust Global Root
12. MIDP2 GeoTrust CA for UTI
13. MIDP2 Nokia Content Signing CA
14. MIDP2 Nokia Root CA
15. MIDP2 Thawte Premium Server CA
16. MIDP2 VeriSign Inc Class 3 Public
17. Nokia Root CA
18. Nokia_Content_SIgning_CA
19. S60 Nokia Root CA
20. Starfield Class 2
21. SymbianA VeriSign Identity-Based ACS Root for Symbian OS
22. SymbianB VeriSign Testing-Based ACS Root for Symbian OS
23. SymbianC GeoTrust Testing-Based ACS Root for Symbian OS
24. SymbianD GeoTrust Identity-Based ACS Root for Symbian OS
25. Thawte Premium Server CA
26. Thawte Server CA
27. ValiCert Class 2
28. VeriSign Class 3 Public Primary Certification Authority
29. VeriSign G2 Class 3
30. VeriSign G2 Class 4
31. VeriSign G3 Class 3
32. VeriSign G3 Class 4
33. VeriSign RSA Secure Server CA


Certificates 1-11 and 17-33 have Internet/Online certif. check/VPN trust settings.

Certificates 12-16 (all MIDP2) have App. installation trust settigns.

Here is the firmware version:
V 1.2.011
28-01-08
RM-421
Nokia N95 (A6.01)

Can someone help me figure out why I am unable to install my signed midlets?

Thanks a bunch.

Hi ngsubs,

And welcome to Forum Nokia Developer Discussion Boards!

So you can install the same app on the device, if you do not sign it?

Is the time and date of your phone set properly?
Are you requesting all necessary permissions in the jad?
How many rows of intermediate certificates do you have in the jad file for the certificate chain? if you have x-3, remove that and try again.

Hartti

Hello Hartti,

Thanks for your response.

I rechecked my device and application configuration, and still encounter installation issues. In response to your questions -

>> Is the time and date of your phone set properly?
Yes

>> Are you requesting all necessary permissions in the jad?
Yes. The same jad/jar works correctly with another unlocked Nokia N73.

>> How many rows of intermediate certificates do you have in the jad file for the certificate chain? if you have x-3, remove that and try again.
I have only 2 certificate chain levels. The jad contains MIDlet-Certificate-1-1, MIDlet-Certificate-1-2, and MIDlet-Jar-RSA-SHA1 properties.


The app's MIDlet-Permissions are set to javax.microedition.io.PushRegistry, javax.wireless.messaging.sms.receive, javax.microedition.io.Connector.file.read, javax.microedition.io.Connector.file.write, javax.microedition.io.Connector.sms, javax.microedition.io.Connector.http

I rebuilt my app, and there was no difference with the installation. Currently I am able to successfully install my app, only via a direct jar access. The app installation via a jad fails with a "Certificate error: Contact the application provider" in the following 2 scenarios -
1) jad with a MIDlet-Certificate-1-n and MIDlet-Jar-RSA-SHA1 entries
2) removing MIDlet-Certificate and MIDlet-Jar entries in the jad hows no difference with the installation

Any other suggestions on how I can install my app via a signed jad?

Thanks again.

Cheers.

Sorry, were you able to install the unsigined MIDlet through the JAD? )this is a little unclear from your response?

In any case, could you post teh jad contents in here?

Hartti

Sorry about the confusion. I am unable to install the unsigned midlet via the jad.

I can only install the app, if I access the jar file directly. Unfortunately the application utilizes a bunch of jad properties so currently the "jar" based installation is successful, but not fully functional. Hope this clarifies the situation

Here is the definition from my unsigned jad -

MIDlet-Jar-URL: app.jar
MIDlet-Jar-Size: 124547
MIDlet-Name: MyApp
MIDlet-Version: 1.4
MIDlet-1: MyApp, /i.png, MyApp
MicroEdition-Configuration: CLDC-1.1
MicroEdition-Profile: MIDP-2.0
MIDlet-Icon: /i.png
MIDlet-Permissions: javax.microedition.io.PushRegistry, javax.microedition.io.Connector.sms, javax.wireless.messaging.sms.receive, javax.microedition.io.Connector.file.read, javax.microedition.io.Connector.file.write, javax.microedition.io.Connector.http
MIDlet-Push-1: sms://:50001,MyApp,*
MIDlet-Data-Size: 3000
MIDlet-Class: MyApp
AppServerURL: [url]http://myserver[/url]
MIDlet-Build: 44


Thanks.

Ok. remove the MIDlet-Build attribute. The specs state that there should be no attributes in the JAD/Manifest which start with MIDlet or MicroEdition and are not defined in the spec

Hartti

Oh, and remove also MIDlet-Class, that is also not allowed

Or if you need those, change the name of those attributes

Hartti