XR 6 min read

Jetpack XR SDK 1.0.0 Is Stable: ARCore and SceneCore GA, What Moves in 1.1 Alpha

On October 21, 2026 the core of the Jetpack XR SDK left preview: androidx.xr.arcore and androidx.xr.scenecore both shipped 1.0.0. The release notes for 1.0.0 itself are short, so this post covers what stable commits you to, the sibling XR Compose beta02 you will actually hit in a build, and the 1.1.0-alpha01 line that opened the same day. If you followed the 1.0.0-beta01 breaking changes, this is the follow-through.

1.0.0
ARCore and SceneCore stable, Oct 21, 2026
beta02
XR Compose, still pre-stable
1.1.0
alpha01 of both libraries opened same day

1. What 1.0.0 Stable Covers

Per the AndroidX release notes, ARCore for Jetpack XR 1.0.0 lists these capabilities: motion tracking, persistent anchors, hit testing, plane identification with semantic labeling (floor, walls, tabletops) and geospatial poses using Google's Visual Positioning System. SceneCore 1.0.0 is described as the library for placing and arranging 3D content as entities: 2D panels and 3D models in virtual and mixed-reality scenes, spatial environments and spatial audio sources, and anchoring virtual content to the real world.

No itemized API list: neither 1.0.0 entry enumerates API changes. The practical meaning of stable is that these surfaces are now what the release process treats as compatible going forward; diff against your last beta build rather than expecting a changelog to tell you.

2. XR Compose Is Not Stable Yet

The UI layer, androidx.xr.compose:compose, was at 1.0.0-beta02 the same day, and the page showed no stable section. It is the library most app code touches, so its notes matter most. Changes in beta02:

dependencies {
    implementation("androidx.xr.compose:compose:1.0.0-beta02")
    testImplementation("androidx.xr.compose:compose-testing:1.0.0-beta02")
}

3. The SceneCore Leak Workaround

This one is easy to miss. XR Compose 1.0.0-beta02 depends on androidx.xr.scenecore:1.0.0-rc01, which has a known memory leak. The release notes say to explicitly override the SceneCore dependency to 1.0.0, which includes the fix. In Gradle that is a direct declaration:

dependencies {
    implementation("androidx.xr.compose:compose:1.0.0-beta02")
    // beta02 pulls scenecore 1.0.0-rc01 (known leak); pin the stable fix
    implementation("androidx.xr.scenecore:scenecore:1.0.0")
}

The notes do not give the exact coordinates, so I used the same scenecore artifact name that the 1.1.0-alpha01 dependency block uses. Confirm in your dependency report that the resolved version is 1.0.0.

4. What 1.1.0-alpha01 Adds

Both libraries opened a 1.1 line on October 21. These are alpha APIs and may change.

ARCore 1.1.0-alpha01

SceneCore 1.1.0-alpha01

// before (deprecated in 1.1.0-alpha01)
animation.start(GltfAnimationStartOptions(/* ... */))

// after
animation.loop = true
animation.speed = 1.0f
animation.start()

The exact property types are my reading of the notes, which list the names but not signatures, so verify against the reference before copying.

What I'd Do

If you are shipping on the stable libraries, pin ARCore and SceneCore to 1.0.0 and treat the 1.1 alphas as a place to prototype, not depend on. If you use XR Compose, expect one more round of source changes before it goes stable, and fix the SceneCore override now. Migrate off the deprecated movable modifiers and DragPolicy today; they are already removed in beta02.

Sources: AndroidX release notes for ARCore for Jetpack XR, XR SceneCore and Jetpack Compose for XR on developer.android.com, all dated October 21, 2026.

Comments 0

No comments yet. Be the first to leave one!

Leave a comment