Created attachment 19028 [details]
How the number ends up in the play store
If you leave the version number unfilled/unset in the AndroidManifest.xml Xamarin Studio or the google api ends up what appears to be a 'garbage' number to it(see attached screenshot). After that you can't undo that by just boosting the number above the bogus versions as Xamarin Studio won't let you set a number higher than 64k(see attached screenshot)
I suspect a piece of code like this:
int versionNumber ;
if( strlen(versionNumberStr) > 0 )
versionNumber = atoi(versionNumberStr) ;
or some similar path
Created attachment 19029 [details]
attempting to set the version code higher the the bogus on part1
Created attachment 19030 [details]
attempting to set the version code higher the the bogus on part2
Created attachment 19045 [details]
When Version Code is removed
curiously those numbers come out to be 0x40001 and 0x20001. Do they get generated if the android:versionCode is absent?
Created attachment 19046 [details]
Result if you try to get the version code to 262146 or higher
So... it's catch22. I can't delete the beta version from the google play store and I can't set the number higher than 64k.
This is probably related to the following code
It used to be that the max versionCode was 65535, bit it seems google has now upped that
" Warning: The greatest value Google Play allows for versionCode is 2100000000."
from the docs at 
Note this cod path is used when emitting an apk per abi. See 
*** This bug has been marked as a duplicate of bug 51620 ***
Notice (2018-05-21): bugzilla.xamarin.com will be
switching to read-only mode on Thursday, 2018-05-25 22:00 UTC.
Please join us on
Visual Studio Developer Community and
GitHub to continue tracking
issues. Bugzilla will remain available for reference in read-only mode.
We will continue to work on open Bugzilla bugs and copy them to the new
locations as needed for follow-up. The See Also field
on each Bugzilla bug will be updated with a link to its new location
After Bugzilla is read-only, if you have new information to add for a
bug that does not yet have a matching issue on Developer Community or
GitHub, you can create a follow-up issue in the new location. Copy and
paste the title and description from this bug, and then add your new
details. You can get a pre-formatted version of the title and
In special cases you might also want the comments:
Our sincere thanks to everyone who has contributed on this bug tracker
over the years. Thanks also for your understanding as we make these
adjustments and improvements for the future.