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

BlackBerry® World™ Development

Error "File bundle (your_name) has been rejected." When Uploading BAR File to BlackBerry® World™

by BlackBerry Development Advisor ‎01-09-2012 10:26 AM - edited ‎12-23-2015 04:00 PM (6,405 Views)

Problem

 

The following error is reported when attempting to upload a BAR file using the BlackBerry® World™ Vendor Portal.

 

File bundle (YOUR_NAME) has been rejected. Package ID is required for all .bar file. If this is an upgrade, Package ID must match Package ID in original file bundle.

 

Cause

 

You are attempting to upload a new version of your application, which contains a different package ID than the previous version.

 

Modifying the package ID for an existing application will prevent users from upgrading to your new release. If a user attempts to install the new version with the modifed package name the application will appear as a second icon on their device and the upgraded application will not have access to the previous application's saved data. 

 

Resolution

 

The package ID is made up of two components, which are the package name of your application and your BlackBerry® Code Signing Key or BlackBerry® ID account (used to create the BlackBerry ID Token for signing). Ensure that the new version of your application uses the same package name and is signed with the same BlackBerry Code Signing Key or BlackBerry® ID account (used to create the BlackBerry ID Token for signing) as the previous version.  If you have linked your BlackBerry Code Signing Key to your BlackBerry ID account, you can sign your with either your BlackBerry Code Signing Key or BlackBerry ID Token (created from the BlackBerry ID account you linked your code signing key to).

 

Workaround

 

If you no longer have access to the code signing keys used to sign your application, you can contact BlackBerry World Vendor Management Support to clear the ID flag for your application, allowing you to update your application.  However, note that if you do this your application upgrade will appear as a new, separate application when downloaded from BlackBerry World.

Contributors
Comments
by New Developer
‎10-23-2015 02:01 PM - edited ‎10-23-2015 02:03 PM

Thanks for this Mark; I'm trying to upload a new version of one of my apps, and getting this error.

"BAR File ('bb10app.bar') has been rejected. Package ID from BAR ('{alphanumeric gibberish}') does not match the application's Package ID ({'different alphanumeric gibberish'})."

When you say
"However, note that if you do this your application upgrade will appears as a new, separate application when downloaded from BlackBerry World."

Can you please confirm that
a) those who have paid for a paid app will not have to pay again, and;
b) the new app will use data already on the device (this I think is doubtful, please correct me if I'm wrong: if the device considers it a new app, the old data would be isolated from the new downloaded app, correct?)

I would like for users of my app to be able to use the existing data, and I of course would like them to not have to have to pay again for the app.

Can you provide a link to any suggested solution for steps to take in my build process to resolve the different Package Id issues? I've tried to associate my old WebWorks 1.0 CSK with my new BBID Token, so perhaps I merged a CSK with my BBID that was different than the one I used to actually sign the BAR file? Can I merge multiple CSK files with my BBID?

 

Thanks in advance

by BlackBerry Development Advisor
on ‎10-23-2015 02:09 PM

Hi ThinkQwick,

 

a)  As long as you upload as a new release of the existing application, users won't need to pay again.

b)  The new application will not be able to access data from the existing application.

 

You can only link one CSK file to a BlackBerry ID account.  If you have multiple barsigner.csk and barsigner.db files you want to test out, remove your existing bbidtoken.csk.  If that file isn't present the signing tools will use the older CSK file.  You can sign some BAR files and check which one matches your original Package-Author-Id listed in the MANIFEST.MF file in the META-INF directory of your BAR file.  Open the BAR file with an archive utility such as Winzip (BAR file is a ZIP file).

 

Mark

Users Online
Currently online: 37 members 734 guests
Please welcome our newest community members: