Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Java Development

Reply
Contributor
bigfoot
Posts: 48
Registered: ‎02-19-2011
My Device: Not Specified
Accepted Solution

Release denied: "attempts to access a secure API"

I got the following message from RIM.  As, you can see it is very terse and not very helpful.  I registered the signing keys carefully according to the instructions so I don't think that's it.  Any ideas what the problem is?

----------------------------------------

Dear App World Vendor,

Unfortunately Release '1.0' from your product has not passed testing and therefore cannot be approved for sale through BlackBerry App World.


If the user starts the application, then the user notices an error message "Error starting GMM: Module ‘GMM’ attempts to access a secure API.". With “OK” option to dismiss the message.

Steps to Reproduce:
1. Wipe the test device.
2. Install the application using Java loader.
3. Launch the application.
4. Notice the above mentioned behavior.

Thank you for your understanding in this matter,

Regards,

The BlackBerry App World™ Team

Please use plain text.
Developer
kiran_b
Posts: 260
Registered: ‎10-27-2010
My Device: 8520

Re: Release denied: "attempts to access a secure API"

drop a mail to devsupport@rim.com

 

 

 

 

 

 

 

------------------------------------------------------------------------------------------------------------------------------------------------------------------

press "Kudos" if it helps

Please use plain text.
Developer
simon_hain
Posts: 15,939
Registered: ‎07-29-2008
My Device: Z10 LE
My Carrier: O2 Germany

Re: Release denied: "attempts to access a secure API"

take care the file is signed. maybe you signed it, but submitted another one, or rebuilt it by accident.
you can open a cod manually with the signing tool to doublecheck.
----------------------------------------------------------
feel free to press the like button on the right side to thank the user that helped you.
please mark posts as solved if you found a solution.
@SimonHain on twitter
Please use plain text.
Contributor
bigfoot
Posts: 48
Registered: ‎02-19-2011
My Device: Not Specified

Re: Release denied: "attempts to access a secure API"

I did not know I had to sign each cod file manually.  I thought once I registered the keys the cod file would be automatically signed each time I built it.

 

Anyway, when I use the Sign sub-menu option on the Blackberry menu nothing seems to happen. My cod file is not updated (sill has the old date stamp on it) and there is no dialog box or message box that tells me it worked or didn't work, etc.  I just get nothing.

 

I am using the BB Eclipse Java plug in.

 

The BlackBerry Signature Tool Developer Guide (which is as clear as mud) says I can check the cod file status using the BlackBerry Signature Tool.  So how do I run the BB Signature Tool?

Please use plain text.
Developer
simon_hain
Posts: 15,939
Registered: ‎07-29-2008
My Device: Z10 LE
My Carrier: O2 Germany

Re: Release denied: "attempts to access a secure API"

there is a SignatureTool.jar file you can execute.
maybe the keys did not integrate with eclipse correctly.
check this directory in your eclipse installation:
plugins\net.rim.ejde\vmTools
it should contain sigtool.csk, db and set. if they are not there, place them there.
----------------------------------------------------------
feel free to press the like button on the right side to thank the user that helped you.
please mark posts as solved if you found a solution.
@SimonHain on twitter
Please use plain text.
Contributor
bigfoot
Posts: 48
Registered: ‎02-19-2011
My Device: Not Specified

Re: Release denied: "attempts to access a secure API"

OK, I think that fixed it Simon.  Thank-you! 

 

I used the cd command to go to the directory containing the SignatureTool, i.e.

 

   D:\Programs\BB_JDE_plugin.1.3.0\plugins\net.rim.ejde\vmTools

Then I ran the tool from the command line using the path to my cod file:

   java -jar SignatureTool.jar D:\workspace\myapp\deliverables\Standard\6.0.0\myapp.cod

 

That brought up a dialog box and I had to enter the private key password, then click a button ('Request' ?), and it seemed to work (I got confirmation messages).  Then I noticed that the time stamp on the .cod file was updated.  

 

Please use plain text.