Android builds (Win): it setps versionName to 1.0

Getting Started Newbie Questions
#1

Hello!
I’ve made a build of my app for Adrnoid using windows version of SDK (build 623, the latest one). In build dialog I’ve set “Version” to 69. But when uploading to android market it shows me that version name is 1.0. But in my case I need to set version code to 1.1 or to 69 to be consistant with my previous builds. Build dialog doesnt allow to specify “.” symbol. So my questions are:

  1. Why it sets version name to 1.0 instead of the value i’m psecifying in build dialog?
  2. How can I set versionName to the value I need? [import]uid: 67485 topic_id: 15705 reply_id: 315705[/import]
#2

Hey,

Just to double check, you have set the version number in two places, yet? Build.settings and then in the window that pops up when you choose to build for Android?

Peach [import]uid: 52491 topic_id: 15705 reply_id: 58166[/import]

#3

The Android build has Version name and VersionCode issue. I specified the version number in build.settings and Corona screen and none of them will show in the final apk. The apk always has 1.0, no matter what you specified in anywhere. Eventually I still went ahead to post it into Android market. I think it is a bug. [import]uid: 42593 topic_id: 15705 reply_id: 58191[/import]

#4

It sounds like it, are you able to file a bug report please? [import]uid: 52491 topic_id: 15705 reply_id: 58335[/import]

#5

I thought the team was aware of this issue, otherwise I’d have reported it myself. There should be a reference to this issue somewhere else in the forum.

@Kynitex
Regardless of being on Win or iOS, the android’s versionCode only sets to full version numbers (1,2,3) while if you try 11 (for v1.1) that is not reflected in the AndroidManifest.xml file within the APK package.
The way I resolved it was to decompile the APK (apktool), edit the AndroidManifest.xml manually, then recompile it and resign it (jarsigner).
All in all, while that was the only solution, you may want to spare yourself this pain and submit a bug report!

Hope that helps [import]uid: 68130 topic_id: 15705 reply_id: 58355[/import]

#6

@peach pellen
On top of the versionCode issue, there is another one I came across when exporting our app to Android. It seems that the option installLocation never gets set to anything other than the default.
I needed to set it to:

installLocation = “preferExternal”

but that didn’t work. For large apps, that’s rather an important setting to have. That was 2 months ago though, not sure if the issue still applies. [import]uid: 68130 topic_id: 15705 reply_id: 58356[/import]

#7

Hi Luca,

My apologies - I don’t normally enter the world of Android :wink: You are correct, yes - Ansca is aware.

As to your other issue, were you testing with a daily or stable build?

Thanks,
Peach :slight_smile: [import]uid: 52491 topic_id: 15705 reply_id: 58552[/import]

#8

Hi Peach,
not 100% sure but I’m pretty positive I was using the last stable build that came out the 2nd of August (591?).
Hope that helps,
Luca [import]uid: 68130 topic_id: 15705 reply_id: 59082[/import]

#9

If you have the time, could you test your build and let me know if it was in fact .591? Happy to pass on the bug for you but need details :wink:

Peach [import]uid: 52491 topic_id: 15705 reply_id: 59268[/import]

#10

Everyone,

We’ve added version name support to the newest daily build, which is available to you if you are a paid subscriber. You cannot set the version name into the build window just yet (we’ll add it in the near future), but you can set the version name via the “build.settings” file as follows…

settings ={ android = { versionName = "2.0" }}[/code] [import]uid: 32256 topic_id: 15705 reply_id: 60914[/import]

#11

Finally!
Thanks a lot!! :slight_smile: [import]uid: 67485 topic_id: 15705 reply_id: 61064[/import]