After getting this error from Gradle in 2019.2.0a9 I finally tracked it down (roughly) to my having (at some point) added support for Google DayDream into the list of supported devices, then having removed it again.
Unity then (probably) failed to correctly update some internal dependencies when you remove DayDream from the list of supported devices, leading to the merging problem with the AndroidManifest.xml. Once I realised that the VrActivityTheme is DayDream only (Android Manifest for Google VR | Google for Developers) I tried adding DayDream back into the list, and suddenly the project could Build and Run.
Somebody might want to look into this a little more deeply.
1 Like
Thanks for bringing this to our attention. The team is aware and we already have a potential fix in the pipeline.
2 Likes
Tried the same approach and it didnt help, should i remove cardboard from the list?
1 Like
The fix is about to land and will most likely arrive in the 2019.2 build we’re planning to release around May 7.
1 Like
Any update on this? Getting the same thing this evening after switching the Build from Oculus to Daydream. Is there a workaround until 2019.2 is out?
I’m having the same problem.
This issue was fixed and backported to 2018.3, 2019.1 and 2019.2.
If you are using a recent version of any of those releases and still experience issues, please submit a bug report for it.
1 Like
I encounter this problem with the project from LWRP VR template on Unity 2019.1.8f1.
I know it’s a preview, but I hope it should be fixed.