Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.2.X, 2019.3.X
Votes
0
Found in
2017.4
2018.4
2019.2
2019.3
2019.3.0b10
2020.1
Issue ID
1198652
Regression
No
Wrong AndroidManifest.xml file is generated after building to Android
How to reproduce:
1. Open the attached "Repro1198652.zip" Project
2. Make sure Vulkan API is in the list of Player > Graphics settings
3. Build the Project
4. Check AndroidManifest.xml <Path to Project>\Repro1198652\Temp\gradleOut\launcher\build\intermediates\instant_app_manifest\release
Expected Behaviour: android:name="android.hardware.vulkan.compute" or android:name="android.hardware.vulkan.version" is in the xml file
Actual Behaviour: android:name="android.hardware.vulkan" is in the xml file even though android.hardware.vulkan is not doccumented in android docs
Reproducible with: 2017.4.35f1, 2018..4.13f1, 2019.2.13f1, 2019.3.0b12, 2020.1.0a14
Note: The issue is specific to Android
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
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Resolution Note (fix version 2018.4):
Backported to 2018.4.16f1