Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2017.4.X, 2018.4.X, 2019.1.X, 2019.2.X
Votes
6
Found in
2017.4.17f1
2018.2.20f1
Issue ID
1118325
Regression
Yes
[Android] Android manifest contains incorrect values for platformBuildVersionCode and platformBuildVersionName
Steps to reproduce:
1. Open the attached project
2. Build for Android
3. Explore the apk's manifest using Android Studio or aapt (~/Android/Sdk//build-tools/28.0.3/aapt l -a build.apk)
4. Notice that platformBuildVersionCode and platformBuildVersionName values are incorrect
Expected result: platformBuildVersionCode is equal to targetSdkVersion (e.g. 28) and platformBuildVersionName is equal to target SDK name (e.g. 9)
Actual result: platformBuildVersionCode is equal to versionCode and platformBuildVersionName is equal to versionName (error.png)
Reproducible with: 2017.4.17f1, 2017.4.19f1, 2018.3.0a1, 2018.3.3f1, 2019.1.0b1, 2019.2.0a3
Not reproducible with: 2017.4.16f1
-
glassfunct
Jun 25, 2019 03:45
Also found in Unity 2018.4.0f1 LTS.
-
smithmj5
Apr 05, 2019 17:00
This still isn't fixed for me in Unity 2017.4.24f1.
-
smithmj5
Mar 08, 2019 01:57
It's worth noting that Unity 2017.4.17f1 has the following in the release notes:
"Backwards Compatibility Breaking Changes
Android: Android Gradle plugin is updated up to version 3.2
Android: Required Android build tools version is increased up to 28.0.3"Found here:
https://unity3d.com/unity/whatsnew/unity-2017.4.17Seems likely that the Android Gradle plugin update is causing the issues.
Is also reproducible on Android 2017.4.22f1, when using Gradle as the "Build System".
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
Resolution Note (fix version 2019.3):
Fixed in 2019.3.0a6
Resolution Note (fix version 2019.2):
Fixed in 2019.2.0b5
Resolution Note (fix version 2019.1):
Fixed in 2019.1.7f1
Resolution Note (fix version 2018.4):
Fixed in 2018.4.4f1