Unity 2017.2 and 5.6.4 not working with GVR 1.110 manifest merging error #789
Comments
Thanks for providing the repro project. I was able to build an Android APK using your project using Unity 2017.2.0p1. I didn't chance any of the settings after opening the TestGVR.zip project you provided. Can you include the full console error messages text you see when you try to build? |
Also, please check that the correct value is set for the Android SDK under "External Tools" section of the Unity preferences. |
Thanks for your quick reply. I have the android SDK set to the root folder with path C:\AndroidStudioSDK. I can build the unity sample program particles demo as an android apk with no problems.
|
It sounds like you might be running into Unity case 888859. If so, you can either:
To try the tools downgrade option:
|
Thanks! This worked for Unity 2017.2.0f3 after applying the tools downgrade. |
If you're doing Daydream development, we recommend you update to the latest 2017.2.0 patch release as 2017.2.0f3 has an issue where the Daydream controller will stop working after background > foreground. |
I only want to build the example scene for cardboard but I am seeing the now well-known manifest merge problem. I even tried testing the custom unity package from the link below but that still didn't build as well.
https://youtu.be/Qn5BCG8SPN8
The previous thread on this topic:
#524
Anyone encounter this old issue again with the latest versions of unity and gvr?
Please download the example project showing this error here:
https://www.dropbox.com/s/e0cerk9r0rwtwsr/TestGVR.zip?dl=0
Found using:
Steps to reproduce the issue:
Best,
Sean
The text was updated successfully, but these errors were encountered: