01-29-2014 03:49 PM
I'm not sure if this question should be asked here or in the blackberry world forum. Please move it if necessary.
So yesterday I suddenly realized it was the last day for the Jam Zone rewards incentive. I had a minor (yet strangely popular) app called Capture The Flag which had a newer version so I quicly packaged it up -- a piece of cake with the Eclipse plugin -- and tried to upload it to Blackberry World. However every time I tried, the upload was rejected because it said the package ID had changed. I know from past experience that you can get this message if the package name changes or if the .bar file has a different name but in this case the package is still com.braincells.capturetheflag and the bar I tried to upload is called capturetheflag.bar just like the previous version.
There are only two things I can think of that changed. 1. Because I am now using the c++ Cocos2D-X framework instead of java, the main activity's name has changed. 2. Hence because of native code, I set the minimum OS required to 10.2.1 whereas before it worked with all versions. Neither of these things should change the Package-Id should they? As a final act of desperation I unpacked the .bar manually edited MANIFEST.MF to use the old Package-Id, repacked and resigned but then I got a different error when uploading which unfortunately I can't recall right now.
So please help me understand what went wrong and how to fix it. Also as I swear I was ready to upload on the 28th, can I please still get the points?
Solved! Go to Solution.
01-30-2014 01:08 PM
Another piece of the Package ID puzzle revolves around your signing keys / developer certificate.
If your signing keys differ from the signing keys that were used to sign the app originally, then you will have a conflict during package id verification and will be unable to submit the updated version.
If this is not the case and you are positive that you have kept your keys the same, you may have re-created your developer certificate with a different author before signing the updated application.
In regards to the jamzone points, it is unlikely that much can be done there. It is an automated process that uses your submission date/time to determine eligibility. With that said, you can try sending an email over to the developer program and see if they have any additional flexibility.
Hope this helps.
01-30-2014 02:10 PM
Thanks for the reply. I don't think my signing key has ever changed. Comparing MANIFEST.MF to an old version again I see that Package-Author and Package-Author-Certificate-Hash are the same. Package-Author-ID is different. Is this significant? A few months ago you added the ability to use a Blackberry ID token instead of a signing key. Is that perhaps being used instead? But I recall the packaging wizard asked me for my keystore and key passwords so I don't think that could be it.
Although this case isn't too important I'm a little worried now that I will not be able to update any of my apps anymore.
01-30-2014 02:36 PM
You are absolutely correct, there may be a step that was missed in here.
We were using two CSJ keys (RDK & PBDT), but now we've shifted to BlackBerry ID Token. If you had keys previously (I'm guessing you did) and then you obtained a BBID Token, you would have needed to go through a linking step.
Most of the information you'll need to link one against the other is in this blog post by Mark Sohm.
blackberry-signer -linkcsk –bbidtoken <BBID Token CSK filename> -oldcskpass <Legacy CSK password> –bbidcskpass <BBID Token CSK password>
Let me know if this helps.
01-30-2014 04:09 PM
I got it now. You need the store password too. Like so:
./blackberry-signer -linkcsk -bbidtoken <path to bbidtoken> -storepass <store password> -oldcskpass <old csk password> -bbidcskpass <bbidtoken password>
01-31-2014 03:00 AM
So to sum up: the problem was that you've used the latest signing method with BB ID, however you didn't link your old keys properly to the BB ID?
Actually I've also missed the Jam Zone promotion's deadline because of a package-id mismatch, though my app was ready well before the 28th. However I still couldn't figure out why my package-id went different, I was still using the old keys to sign.
01-31-2014 07:31 AM
Yes that's it. The beta eclipse packaging wizard asks you for the store and certificate passwords so I assumed that the old signing method was in use and didn't remember at first that I had set up the bbid option or that I hadn't linked it.