02-07-2012 02:39 PM
Great to here! Loads of signing changes/improvements have occurred since the first PlayBook dev tools were released. If you have any more questions I'm happy to provide the answers.
02-09-2012 08:25 PM
Garett, follow-up question:
When I try to verify a signed BAR, which was signed with the old certificate, I get this:
c:\> blackberry-signer -verify alreadysignedbar.bar Info: Bar verified. Warning: This bar contains entries whose signer certificate will expire within six months.
At first I was worried this was going to mean all apps out there which were signed with the original one-year expiry certificates, were going to suddenly become non-functional soon (Feb 17 in my case).
Is it fair to say that this warning is there solely to alert developers that the certificate they used will shortly not be usable to sign new apps? But that the old apps will continue to work without updates, "forever"?
If not, this would suggest everyone has to be generating new certificates, signing updates (bump version number and re-sign), and submitting them in the vendor portal in the very near future. Please tell us nobody has to do that just to keep their apps functional.
02-10-2012 09:01 AM
No need to worry! This is just a warning message, your applications should continue to function even after the p12 certificate expires.
02-24-2012 11:55 PM - edited 02-25-2012 12:17 AM
The certificate I used for my Android app has expired (valid until Feb. 23, 2012). My new certificate is valid until 2032. The -printcert output shows the same Owner CN and Issuer CN for both certificates. However, I cannot deploy a bar file signed with the new certificate if the one signed with the expired certificate is on device. blackberry-deploy returns failure -104
What is failure -104 and what can I possibly do to upgrade my app, which is already published in App World?
I compared MANIFEST.MF between the old and the new bar files. Everything is the same except for the following fields: Package-Version, Package-Author-Certificat
Package-Author-Id, Package-Id and Application-Id are the same.
02-28-2012 09:30 AM
Please start a new thread aas this does not appear to be related to the original topic. Your application seems to be signed correctly and the issue is just with deployment.
02-28-2012 12:22 PM - edited 02-28-2012 12:24 PM
but nobody seems to know the answer.
As it stands now, if your certificate expires, the OS will not allow you to replace the app with a new version. I wonder if App World will accept the new version at all. At least if it will, users can uninstall the old version first and then download the new one.
05-07-2012 05:38 AM
Im confused because the "blackberry-keytool -genkeypair -storepass <storepass> -author <company_name>" command doesnt fit to the official documentation:
Which Version of the keytools do i need?
Can i still use my version (shipped with Tablet SDK 1.0.1) ?
And is the following syntax then the same?
"blackberry-keytool -genkeypair -keystore <certificate_filename.p12> -storepass <storepass> -dname "cn=<company_name>" -alias author
05-07-2012 08:31 AM
The commands have evolved with newer versions of the tools, you should be using the latest SDKs ideally though. To determine which command you should be using open a command prompt to the location of your signing tools and type 'blackberry-keytool' without any arguments, the built-in help will display the command expected to create a p12.