Unity OpenXR Android XR 1.5.1 Raises Its AR Foundation Dependency

An XR project is rarely built from one package alone. The renderer, interaction systems, tracking abstraction, and platform-specific integration each carry their own version requirements. A small dependency change in one package can therefore matter when an otherwise unchanged Unity project is reproduced on another developer's machine.

Unity's OpenXR Android XR integration received version 1.5.1 on October 27, 2026. The official changelog identifies a single change: the minimum AR Foundation dependency moves from 6.7.0 to 6.7.1. This is package maintenance rather than a newly introduced rendering or input capability.

The update follows the AR Foundation 6.7.1 release, which fixed code signing for a native XR Simulation bundle on macOS. While the two changes are related through package version requirements, the Android XR plugin's changelog does not itself claim to repair a headset tracking bug, expand OpenXR features, or improve frame rates.

Developers preparing an Android XR build should be careful about what compatibility means. OpenXR provides a cross-platform interface, but individual devices still differ in supported extensions, interaction modes, performance, and deployment requirements. A version bump in Unity's platform integration does not prove that a PCVR application will run unmodified on a standalone headset or on a pair of connected XR glasses.

The practical first step is to inspect the project's manifest and Package Manager dependency graph. Confirm that the Android XR OpenXR integration, AR Foundation, and the chosen Unity Editor release all satisfy their declared version constraints. Updating one package while pinning an older dependent package can produce confusing restore or compilation failures.

A small XR verification project should contain one simple tracked object, one visible UI element, and one input interaction. Run the project's ordinary build and package-resolution steps, then validate the behavior on the intended physical hardware. If only a simulator is available, record that limitation rather than reporting the test as successful device compatibility.

Teams using the conventional Oculus XR Plugin or developing a Windows PCVR experience have a different toolchain. The Android XR OpenXR package update is not interchangeable with an Oculus-specific release, even if both appear under Unity's broader XR ecosystem.

Maintenance notes like this are rarely spectacular, but they form the foundation of dependable builds. Recording exact package versions and testing upgrades in a separate branch can prevent an apparently harmless dependency change from interrupting an established release pipeline.