Build 336 - Unable to set versionName in Android

I am unable to set the versionName for a build in Build 336. Previously on 268 I can set it in the build dialog, but now the build dialog only accepts integer. I then try to set this in the build.settings file as versionName = “1.1” but unable to do so.

Anyone else know about this issue and how to overcome it?

Cheers [import]uid: 46116 topic_id: 8515 reply_id: 308515[/import]

Hi anyone else has this issue?

I’ve checked the latest build 342 and I can’t still setup my VersionName e.g. 1.1 and 2. I ended up sending my update to Android Market as version 2 when it needs to be 1.1. [import]uid: 46116 topic_id: 8515 reply_id: 31085[/import]

I ran into the same problem and I resorted to just using integers. It seems that the decimal causes a ‘failure to build’ error. [import]uid: 14218 topic_id: 8515 reply_id: 31136[/import]

Android doesn’t allow non-integer version numbers which is why we prevent you from doing that now.
[import]uid: 7563 topic_id: 8515 reply_id: 31155[/import]

Hi ewing,

I was referring to versionName.

http://developer.android.com/guide/publishing/versioning.html

I believe there should be two fields, one is for versionCode which needs to be an integer and this is used internally and with android market but the other versionName which is a string that is displayed to the user and also to your listings in Android marketplace. I did the first few builds on Corona b268 and this is fine (i can do 1.0 and 1.1 for versionName right in the build window).

I tried to set the versionName in the android build setttings and this was also not correctly picked up.

cheers. [import]uid: 46116 topic_id: 8515 reply_id: 31156[/import]

Hi Ansca Team,

Can I please know if anyone looking into this? Because of the constant many stabilization updates I have to make for my Android app in the Android market, I think i will end up with having Version 100 soon!

Cheers [import]uid: 46116 topic_id: 8515 reply_id: 32668[/import]

There is no open bug on this for us so it has not been on our radar. Please submit a formal bug report so we don’t lose track of this. [import]uid: 7563 topic_id: 8515 reply_id: 32705[/import]

Thanks ewing. I’ve submitted bug report Case 4837. [import]uid: 46116 topic_id: 8515 reply_id: 32737[/import]