11-01-2013 03:14 AM
I have an Android application, and I wish to repackage it for BlackBerry. The creation of the .bar file and the signing works fine using the tools integrated in Eclipse (right-click on the project root > BlackBerry Tools > Sign for BlackBerry World).
But I noticed that the version used in the manifest.mf file for the Package-Version and Application-Version is wrong (you can open a .bar file in Eclipse with the BlackBerry plug-in, and it will display the manifest.mf file). The version of my Android application is 3.3.0 in the Android Manifest, and the generated Package-Version is 1.0.330.0.
I already have some releases on BlackBerry World with version 3.x.x, so I can't upload this .bar file because the version is smaller than the other available packages. Does anyone of you know why the version looks like this and how to fix this?
Thank you for your help,
11-03-2013 05:29 AM
There is realy noone able to help me with this?
If you need any additional information, feel free to ask. I would like to publish this app as soon as possible...
11-04-2013 10:29 AM
There is a conversion done to the Android version numbers in order to gernerate a consistent version format.
Depending on the size of your version code, it should be:
Is the other release you've put on App World an Android version?
11-04-2013 11:35 AM
11-06-2013 02:13 PM
Could you point me to your app on App World? I wasn't aware that it was even possible to create a version of an Android app that's not in the format of 1.0.versionCode.0.
11-11-2013 01:39 PM
Here's a copy of my answer for others on the board:
"This is expected. There's a difference between a native application's version number and an Android application version number.
We've employed a technique to better formulate the Android versionName/versionCode scheme to make it more consistent for our platform. There isn't currently a way to arrage versions so that the two differently targeted application's use a single format."