Search Issue Tracker
By Design
Votes
0
Found in
2018.1.0b1
2018.1.1f1
Issue ID
1040342
Regression
Yes
[Android] Version is null if a custom .gradle template is used without "versionName" set
Steps to reproduce:
1. Open QA attached project
2. Build the game to device
3. Go to Settings -> Apps -> "built app name"
4. Observe that version is null
Expected result: version should not be null when custom .gradle template is used
Reproduced in: 2018.3.0a4, 2018.2.0b11, 2018.1.7f1, 2018.1.0b1
Not reproduced in: 2018.1.0a7, 2018.1.0a1, 2017.4.6f1, 2017.3.2f1
Regression since: 2018.1.0b1
Reproduced with:
Huawei Nexus 6P (Nexus 6P), 7.1.2, CPU: Snapdragon 810 MSM8994, GPU: Adreno (TM) 430
Htc 10 (HTC 10), 7.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
Google Pixel (Pixel), 8.1.0, CPU: Snapdragon 821 MSM8996 Pro, GPU: Adreno (TM) 530
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
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
- Crash after the “State comes from an incompatible keyword space“ log when opening the project
- [Android] GameObject are not rendered at all or rendered black when in the custom shader “multi_compile_instancing“ is enabled with two “float4” instance properties are present on older devices
Resolution Note (2018.1.X):
Users build.gradle is incorrect because it is taken from older Unity versions. In order to build on 2018.1, you need to take the default Unity template from 2018.1 and make your modifications on top of that. Same applies for newer Unity versions.