If I use level API 29, background is black and If I don’t use that custom manifest, this is the log: Missing ‘package’ key attribute on element package at AndroidManifest.xml:11:5-75ĪRDKStarted\Temp\gradleOut\unityLibrary\src\main\AndroidManifest.xml Error: If I use a custom AndroidManifest with that queries tag added, I get an error when building:ĪRDKStarted\Temp\gradleOut\unityLibrary\src\main\AndroidManifest.xml:11:5-75 Error: So, my setup: Android 11 (OnePlus7T), Unity 2019 LTS, Gradle 6.9.1, JDK 1.8, no ARCore plugins as I get the merger error (is ARCore required?). If there’s a log display in the scene you’re building, I’d check that for any sort of warnings. The black screen with API 29 is likely a different issue.
various uses-feature and uses-permission tags. various activity, intent, meta-data tags. Įdit the custom AndroidManifest.xml and add a section. More details on how Unity builds generate the Android manifest are available here. You may need to do an initial Android build in Unity, and then copy the generated AndroidManifest.xml in your project’s Temp/gradleOut/unityLibrary/src/main/ to your project’s Assets/Plugins/Android directory. Follow the steps at for your version of UnityĪdd a custom AndroidManifest.xml to your Unity project.
Install gradle v5.6.4 or higher and configure your Unity project to use this version of gradle. I’m working on an ARDK doc update that explains all of the steps, but the basic process is: If you need to use Android 11+ / API level 30+ and are getting that Google Play Services AR popup, you might need to add a “queries” section to your AndroidManifest.
0 kommentar(er)
