This is probably staring me right in the face and im not seeing it, but when updating a xojo app already on the play store with a new build from xojo, how do i change the version of the build on xojo? When uploading an update it tells me on play console that the update has the same version code as the previous version.
Ive tried playing around with the shared settings (Versions) but thats not working 
Many thanks!!
Robin
Bottom of the navigator panel (left hand side). Look at the Shared settings. There is an option there to automatically turn on āAuto Increment Versionā, which increases the non-release version each time you press build. You can choose your versioning there.
Hi Ian,
Iāve been playing around with the versions and auto increment but its still showing the following on Google play Console.
These are version numbers on my updated app
Im actually at a loss on how to proceed.
You need to increase the Non Release Version from 1 to a higher number for each Play Store submission.
Hello
@Paul why is this? The Non Release Version is not what it says it is?
Tim
Thank you Paul, Iāll give that a go In the morning.
Not speaking for Paul, but at least when I was releasing an Android app (non-Xojo), Google was indeed very particular about the version numbers and you were forced to increment the build number otherwise the Play store wouldnāt accept the new version.
Hi Patrick,
Yes, I understand that - but it is a āNon Release Versionā. Meaning to my mini mind that this is a alpha or beta but not production. Whereas the other elements are for Compiled, production versionsā¦
Thatās where my confusion/question comes into play.
Tim
Ah yes, I understand but alas Xojo mobile apps generally need to intersect with other vendorās systems (e.g. Google & Apple) and hence the other half of the equation is owned by someone else other than Xojo. So although Xojo itself has a non-release version (aka build number), I recall Google in particular being pretty forceful in having this always be incremented. So as an example, version 1.0.1.23 youāll be able to upload but 1.0.2.23 wonāt be accepted as theyāll require you to change this to 1.0.2.24 before the Play Store will absorb the app. Iām not disagreeing that thereās some madness to this, but it ends up being someone elseās playground so you need to play by their rules.
Paul might have more info to add here as Iām just relying upon my non-Xojo Android experience. Although Xojo might call this a ānon-release versionā, my guess is that Google actually sees this as a ārelease versionā as they were always super particular about the fourth placement value of the version number.
P.S. If this is all correct, then I might smell a feature request to change the āNon Release Versionā label in the IDE to something more accurate for Android projects.
No, I understand that.
The name of the field, āNon Release Versionā, is misleading. That is what I was getting at.
But now having seen the issue you guys are facing, I can see why that field is important - but again, the label given āNon Release Versionā is misleadingā¦ at least to me.
Thanks Patrick!
Tim
It is the non-release version because it is an internal build number and thus not the release version number. The Android Play Store and the iOS App Store both use it to ensure the uploaded build is different from prior ones. Setting the Auto Increment Version switch is ON ensures the version is automatically increased each time you do a build so you generally donāt have to worry about it.
Maybe changing the nomenclature in the IDE to āBuild Identifierā, āBuild IDā, etc. makes sense @Paul_Lefebvre ?
It feels like āNon-Releaseā has some implicit connotations of āthis number isnāt relevant to the app your releasingā which doesnāt seem to be the caseā¦
Just putting in my two cents; I understand theyāre may be non-obvious-to-someone-who-doesnāt-work-for-Xojo reasons to keep it as it is. 
Itās been āNon Release Versionā for probably 20 years now and its purpose hasnāt really changed over that time.
If people think that name is now too confusing, do create an Issue for it so we can evaluate.