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

Android™ Development


Thank you for visiting the BlackBerry Support Community Forums.

BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)

BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.

"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."

- Kevin Michaluk, Founder, CrackBerry.com

Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.


Reply
Contributor
Posts: 13
Registered: ‎03-13-2012
My Device: playbook
My Carrier: telus

Code Signing Problem

[ Edited ]

I first submitted my android app back in February hoping for a free playbook, however I missed one instance of the word android so it was denied. Unfortunately my laptop that I registered my signing keys on and configured my computer to sign for crashed so I can't get the update signed. When I tried to configure my new computer with the those same codes it came up too many registration attempts (exact "Authentication failed. There have been too many failed attempts"). When I requested new codes the app was signed successfully, however the app world wouldn't register the app as an update (which it needs to do to qualify for the free playbook) because the signing codes were different. The exact error is "File bundle (Aq info[3].bar) 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."

 

Not sure what to do.

 

Any help would be appreciated.

Highlighted
Contributor
Posts: 29
Registered: ‎03-06-2012
My Device: Developer

Re: Code Signing Problem

I think if you lose the certificate you're SOL. That's why they tell you to back it up repeatedly, once you lose it you'll have to make another certificate and your app can no longer be updated.

 

But about the "error", if you're now able to sign it what's the problem? Where does this "error" come up? Have you tried changing the package name in the Android manifest?