Search Issue Tracker
By Design
Votes
0
Found in
2017.4.18f1
2018.3.0a1
2018.3.11f1
2018.4.0f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1152250
Regression
Yes
[Android] Manifest files from .plugin folder are not merged when building Android project
To reproduce:
1. Open attached project "TestAndroidManifestMerger.zip"
2. Build the project for Android platform
3. Check the exported project's generated manifest files
Expected: newly generated manifest file contains data of both merged manifests
Actual: manifests are not merged
Reproduced in: 2017.4.18f1, 2017.4.27f1, 2018.4.0f1, 2019.1.4f1, 2019.2.0b3, 2019.3.0a2
Not reproduced: 2017.4.0f1, 2017.4.17f1
Note1: make sure not to use Export, as it does not merge the manifests
Note2: build.gradle does include the .plugin to the dependencies, however, manifests are still not merged
Note3: file locations of the manifest files that supposed to be merged:
"Assets\Plugins\Android\AndroidManifest.xml"
"Assets\Plugins\Android\GooglePlayGamesManifest.plugin\AndroidManifest.xml"
Output manifest locations:
<Root>\Temp\src\main\AndroidManifest.xml
in 2019.3.0a2: <Root>\Temp\gradleOut\unityLibrary\src\main\AndroidManifest.xml
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
- Console displays "ArgumentException: Cannot unschedule unknown scheduled function UnityEngine..." error after the "Audio Random Container" closing
- [Ubuntu] Asset Bundles Dropdowns Contain Empty Row in Inspector
- Symbols are generated for a third-party native plug-in with 'Shared Library Type' set to 'Executable' when building for Android
- "Search by Import Log Type" Icon Nearly Invisible in Light Theme (Project Window)
- [Android] Realtime Directional Light turns off when there is no realtime shadow caster in the view
Resolution Note (2017.4.0):
Manifests are merged by gradle. The merged version is put directly into the apk.