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

Java 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 Developer
Posts: 12
Registered: ‎03-19-2009
My Device: Not Specified

Different signing keys for minor application release for RIM AppWorld : Will it work or be rejected for version update ?

HI,

I have a question  regarding signing keys validity.

I submitted an application to RIM AppWorld, which has been developed by my sub-contractor.
This subcontractor has a different signature files .(I can not install his signature files on my computer).

The question is about updating an application .. Let's say I have a new release (minor updates release),but this release is signed by my keys , not of my subcontractor keys ..

Can I submit this release as update of previously submitted application (signed by my subcontractor keys) or from RIM AppWorld perspective this update can only go as a New Application , because of my (new) keys ?

Thank you,


Marat

Developer
Posts: 4,764
Registered: ‎07-21-2008
My Device: Not Specified

Re: Different signing keys for minor application release for RIM AppWorld : Will it work or be rejected for version update ?

There is no technical reason why you cannot do this.

 

However, tis is an "App world" question, and should probably be asked on the appropriate forum.

 

New Developer
Posts: 12
Registered: ‎03-19-2009
My Device: Not Specified

Re: Different signing keys for minor application release for RIM AppWorld : Will it work or be rejected for version update ?

Well .. for Android it's different :

 

..... make sure you
safeguard your keystore file! If you lose it and you can’t re-create it, you won’t be able to
update your application, and you’ll have to issue a whole new application instead ....

Highlighted
New Developer
Posts: 12
Registered: ‎03-19-2009
My Device: Not Specified

Re: Different signing keys for minor application release for RIM AppWorld : Will it work or be rejected for version update ?

Official response from RIM : 

 

 

BlackBerry PlayBook application updates *must* be signed using the same keys used to sign the original application or it will be seen as a new application altogether and will be unable to be linked to the original.

 

For BlackBerry smartphone applications the signature applied to the application is not used to differentiate, so updates can be signed by any signature keys without issue.

Developer
Posts: 4,764
Registered: ‎07-21-2008
My Device: Not Specified

Re: Different signing keys for minor application release for RIM AppWorld : Will it work or be rejected for version update ?

OK - please mark the thread "solved".