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

Testing and Deployment

How to verify your BAR file is fully signed

by Retired on ‎03-16-2011 02:08 PM - edited on ‎03-22-2012 04:04 PM by BlackBerry Development Advisor (15,253 Views)

Applications created for the BlackBerry® PlayBook™ tablet are compiled into a .bar file, this file is an archive that contains all of the application code and resources. You are able to open this file using most standard archive applications to see the contents.

 

In the root of this .bar file will exist a META-INF folder, this folder by default contains a copy of the application MANIFEST.MF file only. Once the application is signed new files will get created in this directory.

 

After signing with the Research In Motion® issued RDK key the following two files will appear:

 

  • RDK.EC
  • RDK.SF

 

 

After signing with the developer certificate the following two files will appear:

 

  • AUTHOR.EC
  • AUTHOR.SF

 

If the above 4 files exist in this directory along with the MANIFEST.MF file then your application should be fully signed.

 

A more comprehensive verification mechanism would be to use the following command:

 

blackberry-signer -verify <BAR_File>.bar

This will verify that the signatures have been fully applied and are valid. This is also the same method used by the BlackBerry® App World™ storefront to verify the file before accepting it to the vendor portal.

 

 

Note: After the BAR is created, its contained files should not be modified as this will break the signature

Contributors
Users Online
Currently online: 18 members 2,661 guests
Please welcome our newest community members: