Search Issue Tracker
Fixed in 2017.2.0f3
Votes
37
Found in
5.6.0p3
Issue ID
907071
Regression
No
[Android] Project fails to build using the updated Android SDK Tools 26.0 during the merging manifest files
Reproduction steps:
1. Update Android SDK Tools to 26.0.1 or 26.0.2;
- Android Studio -> Configure -> SDK Manager -> Android SDK -> SDK Tools
2. Create the new project;
3. Switch the platform to Android in the Build settings;
4. Enable "Virtual Reality Supported" and select VR SDKs (Oculus or Daydream) in the Player settings;
5. Build the project;
Actual result: the project does not build and the window "Build failure" shows up with an error "Unable to merge android manifests" (build_failure.jpg).
Expected result: the project should be built on Android platform.
Note: the issue happens only when Android SDK Tools is updated to 26.0, because when it is 25.2.5 version, everything works fine. Also, if "Virtual Reality Supported" is disabled, everything works correctly too.
Reproduced with: 5.4.5p2, 5.5.3p3, 5.6.0p4, 2017.1.0b4
DUT:
Samsung SM G928F*, OS:6.0.1, CPU:arm64-v8a, GPU:Mali-T760, Build:samsung/zenltexx/zenlte:6.0.1/MMB29K/G928FXXS3BPIA:user/release-keys (Reproduced)
Sony D6603 (Xperia Z3)*, OS:6.0.1, CPU:armeabi-v7a, GPU:Adreno (TM) 330, Build:Sony/D6603/D6603:6.0.1/23.5.A.1.291/2769308465:user/release-keys (Reproduced)
Samsung SM G361F*, OS:5.1.1, CPU:armeabi-v7a, GPU:Vivante GC7000UL, Build:samsung/coreprimeveltexx/coreprimevelte:5.1.1/LMY48B/G361FXXU1APB1:user/release-keys (Reproduced)
Merging for Daydram fixed in:
5.4.5p3, 5.5.3p4, 5.6.0p4, 2017.1.0b3
Fix for Oculus coming soon, this will be edited to reflect the changes.
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
jazzpablo
May 27, 2017 08:40
Workaround in the meantime (first shared here https://issuetracker.unity3d.com/issues/android-build-fails-when-the-latest-android-sdk-tools-25-dot-3-1-version-is-used)
1) after a failed building attempt, go to the Temp/StagingArea folder in your Unity project, grab the AndroidManifest-main.xml file
2) copy it into Assets/Plugins/Android, rename it to AndroidManifest.xml
3) in the file itself, remove "android:theme="@style/UnityThemeSelector" and "android:debuggable="true""
With that, at least I'm able to build for Gear VR.
geekthroat
May 25, 2017 01:48
This puts a total stop in GearVR development. Please fix asap!
Aaron-Gibbs
May 25, 2017 00:42
I'm still encountering this as well. Using 5.6.1f1 and the latest SDK 26.02.
Ruhan-
May 23, 2017 13:32
Also still happening on 5.6.1f1 and not patched on 5.6.1p1 it seems based on change log.
I'm afraid to update to API 26.06 or further if it keeps breaking Unity's Android build module.
Ruhan-
May 23, 2017 13:28
This issue needs more votes and I couldn't find it with keywords via google search. Idk might be hard for people with this issue to find and vote on this page.