Search Issue Tracker

Fixed in 2019.3

Planned for 2017.4

Fixed in 2018.4, 2019.1, 2019.2

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

Mobile

-

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

  1. Response avatar

    Resolution Note (fix version 2019.3):

    Fixed in 2019.3.0a6

  2. Response avatar

    Resolution Note (fix version 2019.2):

    Fixed in 2019.2.0b5

  3. Response avatar

    Resolution Note (fix version 2019.1):

    Fixed in 2019.1.7f1

  4. Response avatar

    Resolution Note (fix version 2018.4):

    Fixed in 2018.4.4f1

Comments (3)

  1. 0ceaebff5691247798d35d43008cdaa4?d=mm

    glassfunct

    Jun 25, 2019 03:45

    Also found in Unity 2018.4.0f1 LTS.

  2. 316baa94f58bbb467159adfeb55b9606?d=mm

    smithmj5

    Apr 05, 2019 17:00

    This still isn't fixed for me in Unity 2017.4.24f1.

  3. 316baa94f58bbb467159adfeb55b9606?d=mm

    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.17

    Seems 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

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.