03-16-2012 09:52 AM
03-16-2012 10:13 AM
Mark, for the record, it is the case that the CN= field should exactly match your Vendor Name in the vendor portal, too, right?
Do you know what error occurs if you try to submit an app signed with a certificate with a different CN name?
That's what I'm looking into now. Historically, it didn't matter but they did add some checks regarding signing recently. I'll post here what I find out.
03-16-2012 03:33 PM
FYI you can perform a test similar to BlackBerry App World using the following command:
blackberry-signer -verify yourFile.bar
If this fails, App World will reject it. I'm not sure the cause of this particular case. It looks like it was packaged incorrectly. Please let us know what tool was used to create the bar file.
03-16-2012 07:02 PM
I used the command line tool apk2bar to create the bar file. Then I modified the archive, but when zipping it again I made a mistake (which is expressed in my last post). This fault is made by me, not the tools.
03-18-2012 12:14 PM
The empty directory entries came from using the Linux zip program with something like "zip -r app.bar ...".
Using the "-D" option with that seems to avoid it, so "zip -rD app.bar ...."
Also the reason for the modification was to increment the version number, since there was no obvious way using the command line. This thread seems to show how this should be done for Android: http://supportforums.blackberry.com/t5/BlackBerry-
I guess there is no command-line way to do this with the existing Android conversion tools.