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.
12-10-2013 09:30 AM - edited 12-10-2013 09:43 AM
here's my problem:
I've tested and signed my app "Emoji" and now trying to upload to blackberry world,but it was rejected because of a different Package-ID
my new config.xml is:
and my former config.xml is :
you can see that the 2 id settings are same.
when build in release mode, I got this in MANIFEST.MF file:
and the former build is :
Please help me with this,thanks!!
I think maybe the problem is because I switched to sign with blackberryid ?
webworks 2.0 requires blackberryid,right?
which is not supported in webworks 1.0,right?
Solved! Go to Solution.
12-10-2013 10:40 AM
As you know WebWorks 2.0 uses the new token-based code signing method, which is associated with your BBID account.
To keep the package-id values the same (between an old and new build) in your application MANIFEST.MF file, you must link your old code signing keys with the new token. That way the signing server recognizes your signature and applies the correct one to the compiled BAR file. This is done using the following cli command:
12-10-2013 12:25 PM
Also, the legacy signing keys are still supported in WebWorks 2.0. You are encouraged to upgrade your keys to get the benefits of the BBID signing system, but it is not a requirement.