08-19-2013 04:59 PM
So, this new system is annoying the hell out of me. I followed the steps to link my new BBID token to my old csk files, but apparently that didn't work, as when I went to resign my apps, it spat out a new token, and now the vendor portal won't let me submit updates to my app because the "Package ID" doesn't match the original.
Absolute junk if you ask me. I even tried to restore my old keys and sign the app again, but nope, still doesn't recognize the Package ID. After all the fighting I did with the vendor portal to get my apps approved I now have to deal with this junk.
If you ask me, it's a step back for most developers. From most I've talked to, they don't even want to do this new system until their actually forced too.
08-20-2013 09:40 AM
Sorry to hear you're having problems. The linking step will be part of the setup wizard in the future. But for now linking through the command line would allow you to easily restore your BlackBerry ID token, so you don't have to worry about losing your code signing keys.
Do you have signed versions your old and new BAR files? Open them up in an archive program like Winzip and extract the MANIFEST.MF files located in the meta-inf directory. Compare the values for the Package-Name and Package-Author-Id from both. Is either one different?
They need to be the same for the Package-Id to match. Package-Name is set in the SDK, Package-Author-Id is your identifier when signing.
08-20-2013 10:09 AM
08-20-2013 11:08 AM
If the package-author-id changed then it's then the keys either changed or wasn't linked to your BlackBerry ID account.
Does your new backup include the barsigner.csk and barsigner.db files?