ARCore SDK for Android v1.20.0

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

• Beginning in December 2020, AR-enabled apps built using ARCore SDK 1.11.0 or earlier will no longer be able to host or resolve Cloud Anchors. Apps built with ARCore SDK 1.12.0 or later are unaffected. To learn more about this breaking change, and for instructions on how to update your app, see the Cloud Anchors deprecation policy.

New APIs and capabilities

• Added persistent Cloud Anchors, which let you increase the time-to-live (TTL) of Cloud Anchors to 365 days. With the Cloud Anchor Management API, you can also extend the lifetime of a Cloud Anchor. Use of persistent Cloud Anchors is covered by the new Cloud Anchors deprecation policy.
  • C: Developer guide, ArSession_hostAndAcquireNewCloudAnchorWithTtl, ArSession_estimateFeatureMapQualityForHosting.
  • Java: Developer guide, hostCloudAnchorWithTtl, estimateFeatureMapQualityForHosting.
• Updated image metadata capabilities:
  C: The new ArImageMetadata_getAllKeys and ArImageMetadata_getConstEntry functions let you get image metadata without having to call the Android NDK camera stack APIs. See the developer guide
  Java: The ImageMetaData#get*(int) method now also throws MetadataNotFoundException. See the developer guide.

Deprecations

• The ArImageMetadata_getNdkCameraMetadata has been deprecated and should no longer be called.

Other changes

• Java: Added new persistent_cloud_anchor_java sample app.
• Changed hello_ar_java and hello_ar_c samples to acquire depth images only when tracking is active. This avoids logging unactionable errors when tracking is not active.

Bug fixes

• Fixed an issue where Chrome WebXR immersive-ar stopped working on 64-bit Android Q+.

ARCore SDK for Android v1.19.0

Breaking change affecting previously published 32-bit-only apps

Google Play Services for AR (ARCore) has removed 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. 32-bit-only ARCore-enabled apps that are not updated 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.

New APIs and capabilities

• Added the Instant Placement API, which enables apps to bypass the surface-scanning step for faster AR object placement in a given scene. As the user moves further around the environment, Instant Placement refines and moves the object if needed.
  • C: Developer guide, ArConfig_setInstantPlacementMode, ArConfig_getInstantPlacementMode, ArInstantPlacementPoint, ArFrame_hitTestInstantPlacement.
  • Java: Developer guide, Config.setInstantPlacementMode, Config.getInstantPlacementMode, InstantPlacementPoint, Frame.hitTestInstantPlacement.
  • Added example use of Instant Placement in hello_ar_java sample and hello_ar_c sample.
• Added <queries> element in ARCore SDK's manifest file to support Package visibility in Android 11. This requires apps to build with Gradle 5.6.4 or later and Android Gradle Plugin 3.6.0 or later.

Deprecations

None.

Other changes

• Updated Java and native sample apps to targetSdkVersion 29 (Android 10).
• Refactored hello_ar_java to be easier to read.
• Modified hello_ar_java to have a simpler plane rendering logic.
• Modified augmented_image_java, augmented_image_c, and hello_ar_c to consistently use premultiplied alpha blending.
• Added diffuseTextureAssetName parameter to specify the texture that should used in AugmentedFaceRenderer.createOnGlThread.
• Added calls to Session.close in all Java sample apps to explicitly release native resources when destroying the activity.
• Moved glm code used by samples to third_party/glm from libraries/glm.
• LICENSE file now lists only the dependencies of the ARCore SDK binary and not Maven dependencies of the samples.
• Fixed incorrect license URL in com.google.ar.core Maven POM file.

Bug fixes

• Fixed a crash in hello_ar_c caused by incorrect arguments being passed to ArFrame_transformCoordinates2d in HelloArApplication::GetTextureTransformMatrix.
• Fixed an issue where disabling Augmented Images would not reduce ARCore's CPU utilization rate as expected. Setting a null or empty Augmented Images database now reduces ARCore's CPU usage. Note, however, the CPU utilization is not reduced while Instant Placement is enabled. See ARCore Performance considerations for details.

ARCore SDK for Android v1.18.1

Note: this is a Google Play Services for AR (ARCore) APK-only release (version 1.18.1). The SDK version remains unchanged (version 1.18.0).

Bug fixes

• Fixed a minor issue affecting Google Lens.

ARCore SDK for Android v1.18.0

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

• Added new Depth API that provides a calculated depth image with each frame. Check the list of ARCore supported devices to see which devices support the Depth API.
  • C: Developer guide, ArConfig_setDepthMode, ArConfig_getDepthMode, ArSession_isDepthModeSupported, ArFrame_acquireDepthImage.
  • Java: Developer guide, Config.setDepthMode, Config.getDepthMode, Session.isDepthModeSupported, Frame.acquireDepthImage.

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.

ARCore SDK for Android v1.17.0

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

None.

Breaking & behavioral changes

None.

New APIs and capabilities

• Added APIs for buffering sequential camera frames in a fixed-size texture queue, to support use cases such as multithreaded rendering pipelines.
  • C: Developer guide, ArSession_setCameraTextureNames(), ArFrame_getCameraTextureName().
  • Java: Developer guide, Session.setCameraTextureNames(int[]), Frame.getCameraTextureName().
• Added missing depth sensor usage and target FPS getters:
  • C: Developer guide, ArCameraConfigFilter_getDepthSensorUsage().
  • Java: Developer guide, CameraConfigFilter.getDepthSensorUsage(), CameraConfigFilter.getTargetFps().

Deprecations

None.

Other changes

• Java: Added medium resolution option on the computervision_java sample.

Bug fixes

• Fixed a bug that caused a crash during the first installation of ARCore on certain devices.

ARCore SDK for Android v1.16.0

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.

Breaking & behavioral changes

• Beginning with ARCore SDK 1.16.0, most devices will now return additional supported camera configs with lower GPU texture resolutions than the device's default GPU texture resolution. See the ARCore supported devices for details.

New APIs and capabilities

• Expanded GPU resolutions are now available on more devices through the getSupportedCameraConfigs(CameraConfigFilter) API. See ARCore supported devices for details.

Deprecations

None.

Other changes

• Cleaned up documentation for ArCameraConfigFilter type.

Bug fixes

• Fixed the triangle winding direction in BackgroundRenderer in our samples, allowing it to work with GL_CULL_FACE.

ARCore SDK for Android v1.15.0

Breaking & behavioral changes

• Update: A bug caused this feature to not work in 1.15.0, which is fixed in 1.16.0.
  Beginning with ARCore SDK 1.15.0, some devices will now return additional supported camera configs with lower GPU texture resolutions than the device's default GPU texture resolution. See the ARCore supported devices for details.

New APIs and capabilities

• None

Deprecations

• None

Other changes

• Vertical plane detection works better on surfaces with low visual texture.

Bug fixes

• None

ARCore SDK for Android v1.14.1

Note: This is a Google Play Services for AR (APK) only release.

Bug fixes

• Fixes an issue that caused Google Play Services for AR to crash on some devices

ARCore SDK for Android v1.14.0

Breaking & behavioral changes

None.

New APIs and capabilities

• Added CAMERA_UNAVAILABLE to the TrackingFailureReason enumeration to represent a temporary loss of the camera to another app on the device. After an app regains priority, tracking will resume.
• Adds native error stack traces for some status failures.

Deprecations

None.

Other changes

None.

Bug fixes

• Fixed the Shared Camera sample's black frame flicker when switching between AR and non-AR modes.

ARCore SDK for Android v1.13.0

Breaking & behavioral changes

None.

New APIs and capabilities

None.

Deprecations

None.

Other changes

• Updated the samples gradle plugin to 3.5.0 (fixes "Gradle Sync error: No value has been specified for property manifestOutputDirectory").
• Fixed a compiler warning in C apps ("warning: explicitly defaulted default constructor is implicitly deleted").

Bug fixes

• Apps built with ARCore SDK 1.13 and later now correctly verify that the camera permission has been granted at ARCore session creation time. This check was missing in Google Play Services for AR (ARCore) 1.8 through 1.12, causing apps built with ARCore SDK 1.12 and earlier to fail to create an ARCore session on some devices, but succeed on others.