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

Adobe AIR 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
Highlighted
Developer
Posts: 25
Registered: ‎06-13-2008
My Device: BlackBerry Torch
My Carrier: AT&T
Accepted Solution

Renewing expired signing keys.

I had one of the earlier sets of PlayBook signing keys; the ones with the 1-year expiration term. The certificate .p12 expired last month.

 

I read this thread:

http://supportforums.blackberry.com/t5/Tablet-OS-SDK-for-Adobe-AIR/What-happens-when-the-signing-cer...

 

I do have the original barsigner.csk and the original barsigner.db files, so as per the above article, I should be able to create a new .p12 certificate that would allow me to submit updates to existing application, rather than be seen as a different certificate that would force me to submit all my products as new apps.

 

So, I made sure the original barsigner.csk and barsigner.db files are in the correct locations (on Windows):

C:\Users\<USER>\AppData\Local\Research In Motion

 

... and I ran

 

blackberry-keytool -genkeypair -storepass <PASSWORD> -author "<My Company>"

 

This generated the author.p12 file, as expected,

 

But when I sign with that certificate (I do increase the version number in the bundle, every time), and I try to submit the update to the BlackBerry App World, I still get the infamous message:

 

"Package ID is required for all .bar file. If this is an upgrade, Package ID must match Package ID in original file bundle."

 

As if the certificate I signed with was a new key, and not based on the original .csk and .db files.

 

Any help would be appreciated! 

» Founder of Antair.
» Take a look at my recent work, and get in touch.
Developer
Posts: 6,473
Registered: ‎12-08-2010
My Device: PlayBook, Z10
My Carrier: none

Re: Renewing expired signing keys.

Have you read Mark's post here? http://devblog.blackberry.com/2012/03/package-id-rejected-by-app-world/

It notes that note only the key, but also just the actual package-name field are relevant. Maybe you changed the package name at one point?

Also, do you have the original .p12 still? You could dump it and the new one and compare, to be absolutely certain the author name did not change in some way.

Did you ever request new keys? If so, is there no possibility you've messed up somehow and overwrote the original files with new ones?

Peter Hansen -- (BB10 and dev-related blog posts at http://peterhansen.ca.)
Author of White Noise and Battery Guru for BB10 and for PlayBook | Get more from your battery!
Developer
Posts: 25
Registered: ‎06-13-2008
My Device: BlackBerry Torch
My Carrier: AT&T

Re: Renewing expired signing keys.

Good call!

 

It was a package name issue (a post-build optimization step added a suffix behind the scenes).

 

Thanks!

» Founder of Antair.
» Take a look at my recent work, and get in touch.