versionName in build.settings ignored?

Solar2D Android
#1

I’d like to have version numbers in the format of Major.Minor.Patch when I update my app but it seems like the following entry in build.settings gets ignored or overwritten by the “Version” field in the build dialog:

android =  
{  
versionName = "1.0.1"  
}

Even though the docs say the Version field in the build dialog “determines the version number displayed to the end user, also known as android:versionName”, we still can’t enter decimal/string values.

Any ideas how to get the version to be Major.Minor.Patch or just Major.Minor? I tried the following in the build dialog but still nothing:

101 (hoping to be 1.0.1): when uploading to the android market the version stays exactly like that.

11 (hoping to be 1.1): same thing, android market says the version is 11.

[import]uid: 8446 topic_id: 10580 reply_id: 310580[/import]

#2

We haven’t yet gotten this quite right and have outstanding work items (#4837, 4883) on this.

Currently the versionName is set from the build dialog and can only be an integer. If you need to update your version 1 app in the market but you don’t want to make it version 2, as a workaround you can give it a revised versionCode in the build.settings file and use that as a minor version, e.g. versionCode = “2”.

You can find the details near the end of this link (Version Code):
http://developer.anscamobile.com/content/configuring-projects [import]uid: 6787 topic_id: 10580 reply_id: 38859[/import]

#3

I have published one app with versionCode=2 in the build settings file. Now I want to update this app. I don’t want to update the versionName because I have only updated very minor bugs. How should I do this ? [import]uid: 44599 topic_id: 10580 reply_id: 39125[/import]

#4

@markmiller01, If your app is currently version 2, then you will have to update your app to version 3. [import]uid: 14218 topic_id: 10580 reply_id: 39176[/import]

#5

@snarla, the workaround you suggested isn’t really viable as I wanted the version to show up as 1.0.1 in the Android Market. And using versionCode would only modify the internal revision number, and the app would still be displayed as 1.0. (I know I’m a bit picky on this)

The temporary hacky solution I used was using apktool to make the manifest file editable again then I manually changed versionName=1.0.1, but I strongly DO NOT recommend this method to others as it can damage the final .apk file. [import]uid: 8446 topic_id: 10580 reply_id: 39209[/import]

#6

So if I am following this right, and I have been seeing the same issue with lack of decimals. Is the current way for an app to show up in the Android store as an update really just changing from 1 to 2 and so forth with no placement of 1.1, 1.5 etc… I ask because inside of 3 bug fixes I had to submit as 1 then 2 then 3 since it would not take any .1 .2 .3

Matt [import]uid: 18783 topic_id: 10580 reply_id: 41024[/import]

#7

Right. Currently with Corona SDK, you can only make integer version updates. If you have version 1 of your app, you have to update to version 2. [import]uid: 14218 topic_id: 10580 reply_id: 41028[/import]

#8

This used to work, you could supply the version name in the build dialog, and the version code in build.settings.

I miss that. We could also have two fields in the build dialog.

-Angelo [import]uid: 12822 topic_id: 10580 reply_id: 42009[/import]

#9

Here’s the thing, consumers that download the app will not be able to the Version Name. But they will be able to see the Version Number. So really, make the Version Name like a 2, or 3 etc depending upon what update it is. For the Version Number, I’ve seen on the Android Market you never need to change the Version Number, you could just keep it on Version 1 if you wanted.

Good Luck!

Regards,
Jordan Schuetz [import]uid: 29181 topic_id: 10580 reply_id: 42576[/import]

#10

Or edit the manifest :slight_smile:

http://www.base2solutions.com/walkabout/Corona%20Tips.html [import]uid: 8872 topic_id: 10580 reply_id: 42764[/import]

#11

@Kam … any update on the Mac OS version of the editor?

And/or any update on whether the 591 build of corona solves any of the issues brought up here?

Thanks,
~~Kenn [import]uid: 13859 topic_id: 10580 reply_id: 48965[/import]

#12

… oh wait. I have windows installed on my mac. i forget that sometimes. :slight_smile: [import]uid: 13859 topic_id: 10580 reply_id: 48968[/import]

#13

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: 10580 reply_id: 60915[/import]

#14

Anyone else observed that when you include the versionName = "…
in build.settings as shown above, the build crashes? Happens on mac and windows for at the last few builds (currently .671)
[import]uid: 31041 topic_id: 10580 reply_id: 66858[/import]

#15

Scott,

Make sure to put commas ‘,’ at the end of every table entry in your build.settings file. Just to be safe, add commas to the end of every entry. For example…

settings =  
{  
 android =  
 {  
 versionCode = 201,  
 versionName = "2.01",  
 },  
}

[import]uid: 32256 topic_id: 10580 reply_id: 66898[/import]