Unable to build ARCore scenes apk on mac osx
michelepanegrossi opened this issue · comments
SPECIFIC ISSUE ENCOUNTERED
Unity hangs while trying to build the example scenes. It gets stuck on 'Building scene 0: HelloAR'. I tried with the Hello AR scene and the PersistentCloudAnchors sene. Unity hangs and I have to force quit. No errors or messages in the console at all. I was able to build the persistent cloud anchors scene on a Windows 10 machine and with AR Foundation and the ARCore extensions package on the same mac osx machine.
VERSIONS USED
- Unity: 2019.4.12f, 2019.4.10f, 2019.3.13f
- ARCore SDK for Unity: 1.20.0
- Device manufacturer, model, and O/S: macbook pro, 15 inch 2.3GHz quad core i7, late 2013 running Catalina 10.15.7 trying to build on a Pixel 4 running Android 11
- Google Play Services for AR (ARCore): N/A
On Windows, use:adb shell pm dump com.google.ar.core | findstr /i "packages: versionName"
On macOS, use:adb shell pm dump com.google.ar.core | egrep -i versionName\|packages:
Packages:
versionName=1.20.202550203
Hidden system packages:
versionName=0
Active APEX packages:
Inactive APEX packages:
Factory APEX packages:
- Output of
adb shell getprop ro.build.fingerprint
:
google/flame/flame:11/RP1A.201005.004/6782484:user/release-keys
STEPS TO REPRODUCE THE ISSUE
- Create new unity project in unity 2019.4.12f, switch to Android platform
- Install XR Legacy Input Helpers and HLAPI packages verified versions.
- Import the arcore sdk 1.20.0 unitypackage
- Check the 'ArCore supported' option in Player --> XR Settings
- Set minimum API level to 7.0 and target version 29 (Android 10)
- Set the scripting backend to IL2CPP and target ARM64
- Follow the instructions in this link to upgrade the version of Gradle and change the build settings https://developers.google.com/ar/develop/unity/android-11-build
I am using gradle 6.6.1, copied it into my Documents folder and I am targeting it from the Unity preferences - Open the Persistent Cloud Anchors or Hello AR scene and try to build.
WORKAROUNDS (IF ANY)
ADDITIONAL COMMENTS
See image here
After retrying several times, it is now working. I have no idea what changed as I did nothing differently which is a bit scary. Maybe the package has been updated.