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


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
New Contributor
Posts: 5
Registered: ‎09-25-2012
My Device: PlayBook
My Carrier: N/A
Accepted Solution

No access to original Code Signing Keys

The company I work for hired a third party to develop our mobile app, but then later we took it back in-house.  The third party had already put out a release for us prior to us taking over the code though.  Now I can't get any of the third party developers to send me the csk file(s) that they used to sign the release.  We have a massive update for the app that we are ready to release, but we want it to show as an update to the current release, and not a new app.  It's my understanding that we have to use the same signing keys as before to make this happen though.

 

Assuming I never get the csk(s) from the third party, what are my options?

BlackBerry Employee
Posts: 109
Registered: ‎08-16-2010
My Device: Top Secret BlackBerry 10 device
My Carrier: Bell

Re: No access to original Code Signing Keys

Hi mbamobile,

 

If this is a PlayBook application, just contact us here and we will clear the package ID from your application: https://www.blackberry.com/profile/?eventId=8109

 

After that you can use a new signing key to sign your application and upload it to App World.  The only downside of this is users will have two icons for your application after they download the new release.

 

If this is a BBOS application (.cod files) you can sign your application with another signing key and upload it without any action on our part.

 

Thanks,

 

Jordan

New Contributor
Posts: 5
Registered: ‎09-25-2012
My Device: PlayBook
My Carrier: N/A

Re: No access to original Code Signing Keys

Hi JordanMC,

 

Thanks for the feedback.  Any idea how long it normally takes to get that package ID cleared for the PlayBook?

 

Thanks

Highlighted
BlackBerry Employee
Posts: 109
Registered: ‎08-16-2010
My Device: Top Secret BlackBerry 10 device
My Carrier: Bell

Re: No access to original Code Signing Keys

Hi mbamobile,

 

If you used the form from the link I provided above, it usualy takes us 24-48 hours to respond to those.  After we clear the package ID, you can upload the new release immediately.

 

-Jordan

New Contributor
Posts: 5
Registered: ‎09-25-2012
My Device: PlayBook
My Carrier: N/A

Re: No access to original Code Signing Keys

Excellent.  Thanks for the feedback!