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.
11-03-2012 02:11 PM - edited 11-03-2012 03:21 PM
I once had signing keys that went with a certain company name. Sadly, I lost them. Now, if I request new keys using the same company name, will I be able to sign updates for existing apps that were signed with the old keys?
I ask this, because I fear that the OS might see the update as a different application, because of different signing keys, and might not allow access to the old version's data in the app-storage directory.
11-04-2012 08:53 AM
11-04-2012 09:18 AM
11-05-2012 04:19 PM
11-05-2012 04:22 PM
11-09-2012 03:51 PM
I am still not able to upload my app as an upgrade. I created a new certificate via Flash Builder and signed the app, but still no go. I get the attached error:
When I compare the MANIFEST.MF files of the previous bar file of the app and the current build, the Package-Id and the Package-Author-Id are different. I don't understand why, since - to my belief - I use the same signing keys, but only a different certification file. Is there a way I can verify that?
Any other ideas?
11-09-2012 03:56 PM
11-09-2012 04:01 PM
11-09-2012 04:09 PM