BlackBerry RIMAPPSA2 signing key required — why?

Question

I\'m trying to sign our BlackBerry app, but now it\'s asking for \"RIMAPPSA2\" signing key, which is the signing key for private APIs (which isn\'t allowed in the app world

Answer 1

This might be due to a bug in Eclipse or RIM. You might not be using the RIMAPPSA2 classes.

OK, so its hard to believe but this page might fix the problem for some:

• Frustrations with Blackberry Developer plugins for Eclipse

Basically its a bug, and by changing the Application Descriptor, saving, removing & re-adding the JAR file, the problem is fixed.

Follow-up #1 - might not work:

The above solution enabled me to build & sign the app. Unfortunately the app won't run on the phone Module 'MyApp" attempts to access a secure API.

Follow-up #2 - this worked for me:

I documented a full solution that worked for me here:

• BlackBerry - use own JAR file in own project

In my case, I was importing my own JAR file, and I needed to set that project's build type to be a MIDLET. Setting it as LIBRARY or APPLICATION caused problems.

Answer 2

I've not tried it, as I am waiting for my signing key.

If you use eclipse, you can have following settings that can be turned off.