ARCore Extensions for AR Foundation v1.25.0

Known issues

• None

Breaking & behavioral changes

• None

New APIs and capabilities

• None

Deprecations

• None

Other changes

• None

Bug fixes

• Various bug fixes and performance improvements.

ARCore Extensions for AR Foundation v1.24.0

Breaking & behavioral changes

• ARRecordingManager and ARPlaybackManager are no longer static classes. They will now each need to be a component attached to a GameObject.

New APIs and capabilities

• Added new Custom Data Track Recording/Playback API, augmentations of the recording and playback features that allow developers to record and play back data to and from custom specified tracks, packaged as MP4 recordings. See the Developer guide for more information.
  • Added ARCoreRecordingConfig.Tracks list to allow the specification of additional tracks to record to when producing a recording.
  • Added ARRecordingManager.RecordTrackData() to record data to specified additional tracks when producing a recording.
  • Added ARPlaybackManager.GetUpdatedTrackData() to playback data recorded to specified additional tracks in datasets.
• Added new enum types RecordingResult.SessionNotReady and PlaybackResult.SessionNotReady to indicate that Recording and Playback APIs are unavailable when AR Foundation is resuming/pausing the session.
• Added new setting option Do Not Use in ARCore Extensions Project Settings > Android Authentication Strategy and iOS Authentication Strategy.

Deprecations

None

Other changes

• ARCore Extensions for AR Foundation is now dependent on AR Foundation 4.1.5 and Unity 2019.4.22f1 is the minimum recommended version.

Bug fixes

• Fixed issue where iOS build failed on Unity 2020.2.7 when Script Debugging is enabled.

ARCore Extensions for AR Foundation v1.23.0

Known issues

• ARPlaybackManager.SetPlaybackDataset() returns failure when the session has been disabled but still in a transition state. See the Developer Guide for a workaround solution.

Breaking & behavioral changes

None.

New APIs and capabilities

• Added XRCameraConfigurationExtensions.GetFacingDirection(). This returns a CameraConfigFacingDirection that describes whether ARCore uses a rear-facing (world) camera or a front-facing (selfie) camera.

Deprecations

None.

Other changes

• Upgraded ExternalDependencyManager plugin (formerly PlayServicesResolver) to v1.2.162.
• CloudAnchors and PersistentCloudAnchors samples now display tracking helper messages when the session is not in tracking state.
• Android build now includes Keyless dependencies when ARCoreExtensionsConfig.CloudAnchorMode is not Disabled and Keyless authentication is selected in Edit > Project Settings > XR > ARCore Extensions.
• Dual camera is now supported on Pixel 4 devices. See the supported devices page for more information.

Bug fixes

None.

ARCore Extensions for AR Foundation v1.22.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.
• Support for stereo camera depth is expected to become available in ARCore SDK 1.23.0.

Breaking & behavioral changes

None.

New APIs and capabilities

• New Camera Config Filter APIs, Developer Guide
  • Added ARCoreExtensions.CameraConfigFilter to define the set of properties desired or required by the app, with options for target camera frame rate, and depth sensor usage.
  • Added ARCoreExtensions.OnChooseXRCameraConfiguration to select the desired configuration from the supported camera configuration list.
• New Recording & Playback APIs, Developer Guide
  • Added ARRecordingManager to create datasets containing video and sensor data.
  • Added ARPlaybackManager to playback previously recorded datasets.

Deprecations

None.

Other changes

• ARCore Extensions for AR Foundation is now dependent on AR Foundation 4.1.0-preview.10.

Bug fixes

None.

ARCore Extensions for AR Foundation v1.21.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

None.

New APIs and capabilities

• Added ARCameraConfiguration.GetStereoCameraUsage(). This returns a CameraConfigStereoCameraUsage that describes if and how a stereo camera will be used by ARCore. Support for dual camera depth is expected to become available in ARCore SDK 1.22.0.

Deprecations

None.

Other changes

None.

Bug fixes

None.

ARCore Extensions for AR Foundation 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

• CameraConfigDepthSensorUsages has been renamed to CameraConfigDepthSensorUsage.

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.
  • Added ARAnchorManager.HostCloudAnchor(ARAnchor, int).
  • Added ARAnchorManager.SetAuthToken(string).
  • Added ARAnchorManager.EstimateFeatureMapQualityForHosting(Pose).

Deprecations

• ARCoreExtensionsConfig.EnableCloudAnchors is now deprecated. Use ARCoreExtensionsConfig.CloudAnchorMode instead.

Other changes

None.

Bug fixes

None.

ARCore Extensions for AR Foundation 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.

Breaking & behavioral changes

• ARCore Extensions for AR Foundation is now dependent on AR Foundation 4.1.0-preview.5.
  • To migrate your project from AR Foundation 3.x to 4.x, refer to the Migration Guide.
  • As part of this migration, ARCore must be selected as the Android XR Provider when building for Android. To change this setting, go to Edit > Project Settings > XR Plug-in Management, switch to the Android tab, and select ARCore as the Plug-in Provider.
• To support Android 11, ARCore Extensions for AR Foundation now requires Gradle version 5.6.4 or later. For details, refer to Android 11.

New APIs and capabilities

• Overrode Equals(object), GetHashCode(), and added CopyFrom(ARCoreExtensionsConfig) to ARCoreExtensionsConfig.

Deprecations

None.

Other changes

• Updated C# style for non-public variables and methods. For example, private float m_Foo now reads private float _foo and private void _Bar() now reads private void Bar().
• Unity 2019.4.3f1 is now the minimum recommended version for ARCore Extensions. AR Foundation 4.1.0-preview.5 requires minimal Unity version 2019.4.

Bug fixes

• Fixed #13: Spamming errors when running the App on Editor mode.

ARCore Extensions for AR Foundation 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.

Bug fixes

• Fixed Cloud Anchors Privacy link in the CloudAnchors 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 Extensions for AR Foundation 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.

New APIs

• ARCloudAnchor now implements OnDestroy(), which detaches the underlying native Cloud Anchor object.

ARCore Extensions for AR Foundation 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.

New APIs

• New XRCameraConfiguration API: The extended fields of XRCameraConfiguration are accessible by extension methods, including GetTextureDimensions(), GetFPSRange(), and GetDepthSensorUsages().

Deprecations

• To adapt to AR Foundation's breaking change on renaming the concept of Reference Points to Anchors, the following changes were made on ARCloudReferencePoint APIs:
  • The class ARCloudReferencePoint is deprecated. Use ARCloudAnchor instead.
  • The enum CloudReferenceState is deprecated. Use CloudAnchorState instead.
  • The member ARReferencePointManager.AddCloudReferencePoint(ARReferencePoint) is deprecated. Use ARAnchorManager.HostCloudAnchor(ARAnchor) instead.
  • The member ARReferencePointManager.ResolveCloudReferenceId(string) is deprecated. Use ARAnchorManager.ResolveCloudAnchorId(string) instead.

Other changes

• Unity 2019.3.0f6 is now the minimum recommended version for ARCore Extensions. AR Foundation 3.1.0-preview.6 requires Unity version 2019.3.
• The CloudAnchors sample has been updated to use the new ARCloudAnchor APIs, which previously were the ARCloudReferencePoint API.