Version code

Hello everyone.

Right so basically I uploaded my first game to the google play store today. I later found a bug that I quickly fixed and now want to update it but the google play store says that there already is a version 1 and that I need to change it. I spent a very long time looking for ways to fix this. I changed the version in player settings, I changed the build version, I tried changing the android manifest. Nothing worked. Please help.

 

Did you create a new APK after updating the version values? Try building to a new APK filename, just to confirm.

 

I tried it with 2 different APK filenames before, I just tried again and now I get his error:


CommandInvokationFailure: Gradle build failed.
C:/Program Files/Unity/Editor/Data/PlaybackEngines/AndroidPlayer/Tools/OpenJDK/Windows\bin\java.exe -classpath "C:\Program Files\Unity\Editor\Data\PlaybackEngines\AndroidPlayer\Tools\gradle\lib\gradle-launcher-4.6.jar" org.gradle.launcher.GradleMain "-Dorg.gradle.jvmargs=-Xmx4096m" "assembleRelease"

stderr[

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task 'rocessReleaseManifest'.
> com.android.manifmerger.ManifestMerger2$MergeFailureException: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 20; XML version "2.0" is not supported, only XML 1.0 is supported.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 2s
]
stdout[
:checkReleaseClasspath UP-TO-DATE
reBuild UP-TO-DATE
:extractProguardFiles UP-TO-DATE
reReleaseBuild UP-TO-DATE
:compileReleaseAidl NO-SOURCE
:compileReleaseRenderscript UP-TO-DATE
:checkReleaseManifest UP-TO-DATE
:generateReleaseBuildConfig UP-TO-DATE
repareLintJar UP-TO-DATE
:mainApkListPersistenceRelease UP-TO-DATE
:generateReleaseResValues UP-TO-DATE
:generateReleaseResources UP-TO-DATE
:mergeReleaseResources UP-TO-DATE
:createReleaseCompatibleScreenManifests UP-TO-DATE
rocessReleaseManifest FAILED
12 actionable tasks: 1 executed, 11 up-to-date
]
exit code: 1
UnityEditor.Android.Command.WaitForProgramToRun (UnityEditor.Utils.Program p, UnityEditor.Android.WaitingForProcessToExit waitingForProcessToExit, System.String errorMsg)
UnityEditor.Android.Command.Run (System.Diagnostics.ProcessStartInfo psi, UnityEditor.Android.WaitingForProcessToExit waitingForProcessToExit, System.String errorMsg)
UnityEditor.Android.Command.Run (System.String command, System.String args, System.String workingdir, UnityEditor.Android.WaitingForProcessToExit waitingForProcessToExit, System.String errorMsg)
UnityEditor.Android.AndroidJavaTools.RunJava (System.String args, System.String workingdir, System.Action`1 progress, System.String error)
UnityEditor.Android.GradleWrapper.Run (UnityEditor.Android.AndroidJavaTools javaTools, System.String workingdir, System.String task, System.Action`1 progress)
Rethrow as GradleInvokationException: Gradle build failed
UnityEditor.Android.GradleWrapper.Run (UnityEditor.Android.AndroidJavaTools javaTools, System.String workingdir, System.String task, System.Action`1 progress)
UnityEditor.Android.PostProcessor.Tasks.BuildGradleProject.Execute (UnityEditor.Android.PostProcessor.PostProcessorContext context)
UnityEditor.Android.PostProcessor.PostProcessRunner.RunAllTasks (UnityEditor.Android.PostProcessor.PostProcessorContext context)
UnityEngine.GUIUtilityrocessEvent(Int32, IntPtr)

 

Well that explains it, the build is failing, and is as I suspected. What changed? You said only the build version, but something else has changed. Don't mess with the manifest, and is likely the issue. You might want to revert to your last known good configuration from a back up or from version control. Unless you know exactly what changes you made.

 

I don't have version control setup.

 

And is why I used the word "or"! Then just back out any breaking changes manually, or use a back up. And no need to reply "I don't make back ups" as it won't help.

 

I've reversed the changes I've made but the error remains. I apologize for replies that don't help, I'm new to this forum.

 

You apparently missed a change you made. This is one way to learn to make frequent back ups! Please test with a new project and see if you can build OK.

 

I can build in other projects

 

Great! At least as a last resort you can start over then with the new project.

 

Ok, thanks for trying to help. I guess the bug will just have to stay in the game.

 

That is certainly another option, but would not be my choice. You don't plan to ever update this game? Anyway, remember to make frequent back ups so you don't get into this situation again moving forward

 

Well I can't start over since I've put about 2-3 months into it and I can't find a way to fix it. I've been looking for about 8 hours.

 

It should only take a few hours to copy the assets and code from your broken project to a new project. You would be done by now most likely

 

Thanks for the advice, I'll give it a try tomorrow morning.

 

I found a more simple fix was to change build system from gradle to internal. Thanks for all the help anyway.

 

Upon further investigation, it turns out that the build version numbering is a known issue in earlier versions of Unity. It has been fixed since 2017.4.20f1, 2018.3, and Unity 2019. Can you confirm which version of Unity that you are using? It would not affect the Gradle build process, so there is something else going on if you can't build.

 

Sorry for the late response. I'm using Unity 2018.3.5f1

 

Different issue then

 

Why aren't you trying the same version of Unity that you originally shipped your game with? (I'm assuming you didn't ship with 2018.3.5 since that just released)

 

It was the version I released with. I made sure everything worked with this version before publishing. As I said changing to internal fixed the issue anyway.

 

Which issue? The version issue, or the build problem? There are two separate issues in this thread. Or were you simply trying to re-upload the previous APK because the build was failing?

 

Both.

 

For clarity since all you said was "both", you were previously trying to upload the previous version APK when you thought the build was actually succeeding. Subsequently we realized that the build was failing, so you were simply trying to upload the same APK again. Once you got the build working, the version issue went away since the new APK now has the new version information in it. Got it!