The new apk needs to be re-signed with the original keystore file.Rebuild with apktool build $OUTPUT_FOLDER.Open the apktool.yml text file and alter the versionCode entries.Open a command line and call apktool d $APK_PATH -o $OUTPUT_FOLDER.Build your Xamarin Android project with any version code between 0.

If you do not want to end like this guy on stackoverflow, follow these steps to update your version code after Xamarin.Android builds your apk. If you distribute separate ABI-packages to Google Play, you need another way to go. But it can lead in a bloated apk file depending on the selected ABIs configured under the 'Advanced'-tab. Both suggest to disable the 'Generate one package (.apk) per selected ABI' option under the Android Build settings. Searching for a solution I came to this question at the Xamarin forums and bug ticket 51620 - which is not accessesible anymore due to the move from bugzilla to github. Google Play accepts version codes up to 2.100.000.000 according to the documentation. That is not a problem in general as the max value of an integer is big enough. We have seen some configurations going that way. One to mention is the case if you are using the entire build date as your version code.

Yet, there are cases that can lead you into this trouble. It is counting up the build number and set that as the version code. We took a look at the build process and couldn't find anything that is obvious. As we first heard about that issue we wondered how this could happen.

Xamarin apk