08-01-2014 09:43 AM - edited 08-01-2014 09:52 AM
So it all started when I thought Ive lost my original signing key generated from on the Blackerry website from my blackberry Id. Before I managed to upload previous version of the application to the Blackberry World.
After a while I decided to request another key, sign the updated app with it and upload it again to the Blackberry World correctly assuming that it will cause problems as it wont be compatible with old version. Ive read lots of threads on that one so I know this is "the right" thing that should happen. Package-Id is different so there is no excuse.
HOWEVER - I managed to dig out the original bbidtoken.csk and author.p12 after like 1 month or so from some old backup. I though - great - I will just replace these files and we are ok...But it appears that after signing it again with command:
blackberry-signer -verbose -bbidtoken bbidtoken.csk -cskpass my_pass_here -keystore author.p12 -storepass my_store_pass_here my_file.bar
I still get the same-new Package-Id in the manifest? Is there some kind of a explanation for this? Is there a way to get back now?
08-01-2014 10:23 AM
It was my mistake, config.xml had a misspelling in the package name so thats why the original key was producing same Package-Id as the new keys did, but does it mean that I could get the same result with new signing files?
08-07-2014 11:51 AM
The Package-Id is derived from the Package-Name and your code signing keys. So if those two are the same you'll be all set. Also, if you are using BlackBerry ID Tokens for signing, you can download a new token and sign with it as long as you use the same BlackBerry ID account. More details on that can be found here: Code Signing Keys Be Gone! Welcome BlackBerry ID