Skip to content

ARCore SDK for Android v1.18.0

Compare
Choose a tag to compare
@bsanjin bsanjin released this 25 Jun 19:21

Upcoming breaking change affecting previously published 32-bit-only apps

In August 2020, Google Play Services for AR (ARCore) will remove support
for 32-bit-only ARCore-enabled apps running on 64-bit devices. Support for
32-bit apps running on 32-bit devices is unaffected.

If you have published a 32-bit-only (armeabi-v7a) version of your
ARCore-enabled app without publishing a corresponding 64-bit (arm64-v8a)
version, you must update your app to include 64-bit native libraries before
August 2020. 32-bit-only ARCore-enabled apps that are not updated by this time
may crash when attempting to start an augmented reality (AR) session.

To learn more about this breaking change, and for instructions on how to update
your app, see https://developers.google.com/ar/64bit.

Known issues

  • Issue 141500087: When using Android Emulator x86_64 system images on macOS with ARCore SDK 1.16.0 or later, Google Play Services for AR will crash. As a workaround, use an x86 system image.

Breaking & behavioral changes

  • targetSdkVersion inside the ARCore Android Archive (AAR) file has been updated to API level 29. Specifying a targetSdkVersion in your project's build.gradle or AndroidManifest.xml will override the ARCore value.

New APIs and capabilities

Deprecations

None.

Other changes

  • Updated Java and native HelloAR sample apps to include Depth API usage.
  • Migrated Augmented Faces Java sample app from Sceneform to direct OpenGL calls.

Bug fixes

  • Fixed Cloud Anchors Privacy link in the cloud_anchor_java sample app. The incorrect link now redirects to the correct link, so existing apps with the incorrect link don't need to be updated.