Skip to content

Releases: google-ar/arcore-android-sdk

ARCore SDK for Android v1.37.0

10 May 20:41
Compare
Choose a tag to compare

Known issues

  • #1573: On certain devices, enabling 60FPS mode causes the tracking to become unsynchronized with the camera feed. The 60FPS mode has been temporarily disabled on these devices and will not appear in supported camera configurations.

New APIs and capabilities

Scene Semantics

Scene Semantics provides richer details about the surrounding scene, making it easier to understand the world around the user. Scene Semantics runs an ML model on the camera image feed and provides a semantic image with each pixel corresponding to one of 11 labels of outdoor concepts.

See Introduction to Scene Semantics and the semantics_java sample app for more information.

Kotlin/Java:

C:

Streetscape Geometry

Streetscape Geometry is a new ARCore Geospatial API that provides the geometry of buildings and terrain in an area around the user when the Geospatial API is enabled.

See Streetscape Geometry Developer Guide (Kotlin/Java) and Streetscape Geometry Developer Guide (C) for more information. Additionally, the geospatial_java sample app has been updated to include Streetscape Geometry.

Kotlin/Java:

C:

Rooftop anchors

Rooftop anchors are a new Geospatial anchor type that helps you anchor content to a rooftop.

See Geospatial anchors (Java) and Geospatial anchors (C) for more information. Additionally, the geospatial_java sample app has been updated to include Rooftop anchors.

Kotlin/Java:

C:

Geospatial Depth

When both the Depth API and Streetscape Geometry modes are enabled in an ARCore session in areas with VPS coverage, the generated depth images are improved using Streetscape Geometry. Streetscape Geometry is integrated into each generated depth image out to a range of 65.535 meters. No changes are needed when calling the Depth API to see this benefit.

See Geospatial Depth (Java) and Geospatial Depth (C) for more information.

Vulkan rendering support

ARCore now provides Vulkan rendering support by exposing the camera image through an AHardwareBuffer. You can use this Hardware Buffer by binding it to a VkImage.

See Rendering your ARCore application using Vulkan and the hello_ar_vulkan_c sample app for more information.

Java:

C:

Electronic Image Stabilization (EIS)

You can configure ARCore to use Electronic Image Stabilization, which smooths camera frames for a more fluid user experience.

See Enabling Electronic Image Stabilization and the hello_eis_kotlin sample app for more information.

Kotlin/Java:

C:

ARCore async APIs

This release introduces new ARCore async APIs to improve ergonomics when working with asynchronous operations, following the Future paradigm.

Java:

  • Resolving Terrain anchors: Use [Earth.resolveAnchorOnTerrainAsync()] to obtain a [ResolveAnchorOnTerrainFuture]. The old symbol [Earth.resolveAnchorOnTerrain()] has been deprecated and may be removed in a later version of ARCore.
  • Resolving Cloud anchors: Use [Session.resolveCloudAnchorAsync()] to obtain a [ResolveCloudAnchorFuture]. The old symbol [`Se...
Read more

ARCore SDK for Android v1.36.0

03 Mar 23:34
Compare
Choose a tag to compare

Other changes

ARCore SDK for Android v1.35.0

08 Dec 01:23
Compare
Choose a tag to compare

New APIs and capabilities

Geospatial pose accuracy

All Geospatial poses now expose their orientation accuracy of the Yaw rotation, replacing heading accuracy.

Deprecations

Other changes

ARCore SDK for Android v1.34.0

12 Oct 22:37
Compare
Choose a tag to compare

New APIs and capabilities

Check Geospatial VPS availability

A new ARCore Geospatial API has been added to check for Visual Positioning System (VPS) availability at a specified horizontal position at runtime. This API can be used without an active AR session, for example, to present an "Enter AR" button only when VPS is available.

Geospatial pose orientation

Geospatial poses now expose their orientation in 3D space.

Geospatial pose conversions

Geospatial poses can now be converted to and from world-space poses.

Note that Geospatial poses obtained from these functions have a heading value set to zero. Instead, use its EUS quaternion instead.

Other changes

  • The geospatial_java sample has been adjusted to check for VPS availability.
  • The geospatial_java sample now supports creating a Geospatial anchor by tapping on the AR camera view.
  • Updated Kotlin samples to Kotlin version 1.5.30 from 1.4.20.

Bug fixes

  • Fixed "Device Not Supported" being reported for emulator images on ARM host machines.
  • ArEarth_getEarthState() and ArAnchor_getTerrainAnchorState() now correctly return ERROR_NOT_AUTHORIZED when there is an authentication issue instead of returning ERROR_INTERNAL.

ARCore SDK for Android v1.33.0

18 Aug 18:25
Compare
Choose a tag to compare

Breaking & behavioral changes

  • To use Cloud Anchors, you must now enable the ARCore API instead of the older ARCore Cloud Anchor API, which is now deprecated. To support older app versions, you may enable both while making the transition. Apps built with ARCore SDK 1.32.0 and lower will target the older API, while apps built with ARCore SDK 1.33.0 and higher will target the new API. Note the following:
    • The new API uses the domain name arcore.googleapis.com instead of arcorecloudanchor.googleapis.com.
    • If you are using an API Key which is restricted by API, you must allow the ARCore API.
    • If you send requests to the ARCore Cloud Anchor Management API from your backend, you must also change the domain name to arcore.googleapis.com, after enabling the ARCore API.
    • The old API/endpoint will continue to be supported through August 2023.
    • See ARCore 1.33 Cloud Anchor endpoint changes for more details.
  • ArImage has been removed. Use android.media.Image instead.
  • targetSdkVersion inside the ARCore aar has been updated to API level 33. Specifying a targetSdkVersion in your project's build.gradle or AndroidManifest.xml will override the ARCore value.

New APIs and capabilities

ARCore Geospatial Terrain anchor API - new

The new ARCore Geospatial Terrain anchor API can create an anchor at a specified horizontal position and altitude relative to the horizontal position's terrain.

Other changes

  • Updated Java and native sample apps to targetSdkVersion 33.

ARCore SDK for Android v1.32.0

24 Jun 19:14
Compare
Choose a tag to compare

Breaking & behavioral changes

  • ARCore's targetSdkVersion has been updated to Android API level 32. If your app does not specify a targetSdkVersion, your app's targetSdkVersion will become 32 due to manifest merging. Specifying a targetSdkVersion in your project's build.gradle or AndroidManifest.xml will override ARCore's targetSdkVersion value.

Other changes

  • Updated Java and C sample apps to targetSdkVersion 32.

Bug fixes

  • The known issue in Google Play Services for AR (ARCore) version 1.31 where configuring a session with GeospatialMode.ENABLED while the session is running may cause the session to hang has been fixed.

ARCore SDK for Android v1.31.0

11 May 18:45
Compare
Choose a tag to compare

Breaking & behavioral changes

  • Updated ARCore's minimum supported Android API level to 19 (from 18).
    • The upcoming Android NDK version (r24) will remove support for Android API levels v16-18.
    • For more information, see the Android NDK r23 changelog.

New APIs and capabilities

ARCore Geospatial API - new

The new ARCore Geospatial API utilizes data from Google Earth 3D models and Street View image data from Google Maps to enable your app for immersive, global-scale, location-based augmented reality experiences.

  • Kotlin/Java reference

    • Earth provides localization ability in geospatial coordinates.
      • Earth.createAnchor() creates a new Anchor at the specified latitude, longitude, altitude, and orientation.
    • Earth.Earthstate describes the current state of Earth, including its TrackingState.
    • GeospatialPose describes a specific latitude, longitude, altitude, and compass heading.
  • C reference

    • ArEarth provides localization ability in geospatial coordinates.
      • ArEarth_acquireNewAnchor() creates a new Anchor at the specified latitude, longitude, altitude, and orientation.
      • ArEarthState describes the current state of ArEarth, including its ArTrackingState.
    • ArGeospatialPose describes a specific latitude, longitude, altitude, and compass heading.

ARCore Depth API improvements

The maximum range of Depth measurements has increased from 8191mm to 65535mm when building with ARCore SDK 1.31 and later. The Depth API now uses all 16-bits to represent depth, where previously only 13 bits were used for depth values.

To reflect this change in behavior, some Depth API functions have new names and behavior changes. The old versions of these functions will have no change in behavior, though it is recommended to make use of the longer depth range. For more information, see ARCore Depth changes in ARCore 1.31.

  • Kotlin/Java
    • The Depth API function calls have changed:
      • Frame.acquireDepthImage() has been deprecated in favor of Frame.acquireDepthImage16Bits().
      • Frame.acquireRawDepthImage() has been deprecated in favor of Frame.acquireRawDepthImage16Bits().
      • The output image formats for both calls have changed from
        android.graphics.ImageFormat.DEPTH16 to
        android.hardware.HardwareBuffer.D_16.
      • Depth is still represented as a 16-bit integer in units of
        millimeters, but now all 16-bits are used to represent depth, allowing
        for a maximum expressible range of 65535mm (previously 8191mm).
  • C
    • The Depth API function calls have changed:
      • ArFrame_acquireDepthImage() has been deprecated in favor of ArFrame_acquireDepthImage16Bits().
      • ArFrame_acquireRawDepthImage() has been deprecated in favor of ArFrame_acquireRawDepthImage16Bits().
      • The output image formats for both calls have changed from AR_IMAGE_FORMAT_DEPTH16 to AR_IMAGE_FORMAT_D_16.
      • Depth is still represented as a 16-bit integer in units of
        millimeters, but now all 16-bits are used to represent depth, allowing
        for a maximum expressible range to go 65535mm (previously 8191mm).

Deprecations

  • Kotlin/Java

    • The Depth API function calls Frame.acquireDepthImage() and
      Frame.acquireRawDepthImage() are deprecated. Please use
      Frame.acquireDepthImage16Bits() and Frame.acquireRawDepthImage16Bits()
      instead.
  • C

    • The Depth API function calls ArFrame_acquireDepthImage() and
      ArFrame_acquireRawDepthImage() are deprecated. Please use
      ArFrame_acquireDepthImage16Bits() and
      ArFrame_acquireRawDepthImage16Bits() instead.

Known issues

  • Configuring a session with GeospatialMode.ENABLED while the session is running may cause the session to hang. This issue will be resolved in Google Play Services for AR (ARCore) version 1.32. In the meantime, ensure your app only sets a configuration with GeospatialMode.ENABLED while the session is paused.

Other changes

  • HelloAR sample apps now visualize the Depth API representing longer-range
    depth values with new colors.

ARCore SDK for Android v1.30.0

03 Mar 21:54
Compare
Choose a tag to compare

Known issues

  • None

Other changes

  • Annotated API return values with @NonNull and @Nullable.
  • Updated the build tool versions used for building samples: Gradle to 7.0.2 and Android Gradle plugin to 7.0.4. Upgrading these tools is not required for existing ARCore applications. For new features, known issues, incompatibility information, see Android documentation on Android Gradle plugin.

ARCore SDK for Android v1.29.0

13 Dec 17:27
Compare
Choose a tag to compare

Known issues

  • None

Breaking & behavioral changes

Other changes

Bug fixes

  • persistent_cloud_anchor_java: Added a missing build dependency to the sample. Fixes a bug where hosting any anchor would have state CloudAnchorState ERROR_NOT_AUTHORIZED even if the project was set up correctly.

ARCore SDK for Android v1.28.0

04 Nov 01:12
Compare
Choose a tag to compare

Known issues

  • None

Breaking & behavioral changes

New APIs and capabilities

  • None

Deprecations

  • None

Other changes

  • None

Bug fixes

  • None