ARCore SDK for Unity 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 changes

• None.

New APIs

• None.

Deprecations

• None.

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.

Other changes

• Removed XPSessionStatus.cs, as it is not used in the SDK anymore.
• As of Unity v2020.1, the Player Settings > XR Settings has been removed. The ARCore Supported option is no longer needed. The ARCore SDK for Unity automatically detects the presence of the SDK, or warn if there is a conflict with components of AR Foundation.

Bug fixes

• Fixed #660: The pawn in the Object Manipulation sample can't be translated.