V2.55.0

[doranteseduardo]

ReactVision ViroCore 2.55.0

This release lands the OpenXR backend for Meta Horizon OS,
a per-source input pipeline that lets multi-pointer backends like Quest
dispatch hover and click independently without breaking single-pointer backends,
and a new Studio scenes API in the bundled Cloud Anchor SDK.
It also ships three platform fixes — Android 2025 ABI compliance, an AR image-marker regression,
and continued iOS portal stability work.

User-facing JS components and hooks built on top of these native changes
(ViroXRSceneNavigator, StudioSceneNavigator, useAnySourceHover,
useAnySourcePressed, the isQuest / hasOpenXRSupport constants, and
the platform guards on ViroARSceneNavigator / ViroVRSceneNavigator)
are documented in the companion Viro 2.55.0 release notes.

---

Highlights

OpenXR backend for Meta Horizon OS

Native VR rendering on Meta Quest 3 / Quest Pro / Quest 2 / Quest 1 via
Khronos OpenXR. Validated end-to-end at 90 Hz on Quest 3 with App = 5–6 ms
frame time. The backend covers the full Activity / surface / session
lifecycle plus input and presentation:

• ViroViewOpenXR.java — Android view selected by the bridge when the
  package is registered with ReactViroPackage.ViroPlatform.QUEST. Defers
  Renderer construction until onAttachedToWindow so xrCreateSession
  binds to the Activity that actually owns the surface — resolved via
  window-token matching against live activities from ActivityThread,
  the only signal that's stable under Android's multi-resumed mode.
  Idempotent onResume / onPause (mResumed boolean) tolerate the
  multi-source RN lifecycle (Application.ActivityLifecycleCallbacks +
  RN LifecycleEventListener firing for the same Activity transition).
  Null-guards every base-class setter / getter that touches the deferred
  renderer.

• VROSceneRendererOpenXR.cpp — C++ scene renderer.
  XR_SESSION_STATE_IDLE → READY → SYNCHRONIZED → VISIBLE → FOCUSED,
  per-frame xrWaitFrame / xrBeginFrame / xrEndFrame,
  projection-layer compositor submission, swapchain image acquisition and
  release. onResume and onPause are idempotent (early-return when
  already in the target state) so the renderer survives lifecycle events
  arriving from multiple sources without re-assigning the render
  std::thread.

• VROInputControllerOpenXR.{h,cpp} — action-based input controller.
  Per-frame xrSyncActions for Touch controllers (triggers, grips,
  A / B / X / Y, menu, thumbsticks, haptics) and per-hand
  xrLocateHandJointsEXT + XR_FB_hand_tracking_aim for fingertip-aimed
  pointing. Pinch-to-click via FB pinch strength with a thumb-to-index
  joint-distance fallback; grip-to-grab via middle-tip-to-palm distance.
  Two-pointer dispatch. Right and left aim poses are captured without
  dispatching, then dispatched once per side via a dispatchSide lambda:
  updateHitNode(source, …) → onMove(source, …) →
  processGazeEvent(source) → laser update. Per-source pose hysteresis
  (~5-frame cache) keeps the aim source from flipping between controller
  and synthesized hand pose on transient single-frame xrLocateSpace
  invalidity.

• VROInputPresenterOpenXR.h — visual presenter. World-space
  (non-headlocked) reticle plus a per-source
  unordered_map<int, Laser> of cyan VROPolyline children under the
  presenter _rootNode, lazy-initialized on first dispatch and hidden
  cleanly when no aim is available. Both lasers can be visible
  simultaneously when both hands are tracked.

• OpenXR extensions in use: XR_KHR_opengl_es_enable,
  XR_KHR_android_create_instance, XR_FB_passthrough,
  XR_FB_display_refresh_rate, XR_EXT_hand_tracking,
  XR_FB_hand_tracking_aim. com.oculus.feature.PASSTHROUGH must be
  declared in the Android manifest for XR_FB_passthrough to be advertised
  by the OpenXR runtime — the Viro Expo plugin emits this automatically
  when xRMode includes "QUEST".

The integration goes deep into the dual-Activity story: surface mounted
inside the VR Activity, xrCreateSession bound to it (not to MainActivity),
the OpenXR session machine cycling cleanly to FOCUSED, the input dispatcher
producing stable hover / click events across both pointers, and reflection-
based VR Activity discovery from the launcher module so exitVRScene
finishes the right Activity even when the React context's currentActivity
remains pinned to MainActivity.

Per-source input state in VROInputControllerBase

VROInputControllerBase previously carried a single _hitResult,
_lastHoveredNode and _lastClickedNode — fine for single-pointer backends
(iOS / AR / Cardboard / OVR / Daydream / Wasm), wrong for multi-pointer
backends like OpenXR where two simultaneously tracked hands need
independent hover and click resolution.

This release adds additive per-source state without breaking any
existing backend:

• New maps _hitResultsBySource, _lastHoveredNodesBySource,
  _lastClickedNodesBySource keyed by input source ID.
• New overload updateHitNode(int source, camera, origin, ray) writes both
  the per-source map and the legacy _hitResult for backward compat.
• New helper getHitResultForSource(source) falls back to the legacy
  _hitResult when no per-source entry exists.
• processGazeEvent and onButtonEvent use the source-aware lookups when
  an entry is present and dispatch hover / click events independently per
  source. Otherwise they behave exactly as before.

iOS, AR, Cardboard, OVR, Daydream and Wasm — which all call
updateHitNode(camera, origin, ray) without a source parameter — see zero
behavior change. Only the OpenXR backend opts into per-source state by
calling the new overload.

Studio scenes API in libreactvisioncca

The bundled Cloud Anchor SDK (libreactvisioncca, shipped inside
virocore) gains two new endpoints that power the Studio scene fetcher in
@reactvision/react-viro:

• getScene(sceneId, callback) — wraps
  GET /functions/v1/scenes/{scene_id}. Returns the full scene response:
  metadata, asset list with placement and material configs, animations,
  collision bindings, scene functions, project info.

• getSceneAssets(sceneId, callback) — wraps
  GET /functions/v1/scenes/{scene_id}/assets. Asset-list-only variant
  for clients that already have scene metadata cached.

Both authenticate with the project API key and return their result inside
the existing ApiResult<T> wrapper. The full asset shape (SceneAPIAsset)
and scene-response shape (SceneData) are added to RVCCAApiTypes.h for
direct C++ consumers.

The endpoints are exposed to JS via
ViroARSceneNavigator.rvGetScene(sceneId) and
ViroARSceneNavigator.rvGetSceneAssets(sceneId). Existing Cloud Anchor and
Geospatial endpoints are unchanged.

---

Fixes

• 16 KB .so page alignment for libvrapi.so (Issue A). The Android
  2025 ABI requires all shipped .so files to align to 16 KB pages.
  libvrapi.so is now repackaged with -Wl,-z,max-page-size=16384,
  resolving load failures on devices with the new page size.

• AR Image Markers — children fixed-on-screen after re-detection
  (Android, GitHub viro #465).
  Models parented to a ViroARImageMarker no longer pin to screen
  coordinates after the target was lost and re-acquired in v2.54.0. Markers
  re-anchor cleanly to the detected world pose every time, including
  subsequent re-detection.

• iOS ViroPortalScene portal-tree stability
  (GitHub viro #452).
  Continued portal-render-pass hardening on top of the v2.54.0 fix
  (VROPortalTreeRenderPass.cpp + VROPortal.cpp):

  • Portal stencil silhouette no longer drops transparent entry fragments
    before the alpha-discard modifier runs
    (_silhouetteMaterial->setAlphaCutoff(0.0f)).
  • 360° background inside a portal is no longer overwritten by the AR
    camera background drawn afterwards (depth = 0.9999 plus depth-write
    enabled on the portal background sphere / cube).
  • The interior of a portal hole no longer reveals the portal interior
    when the user is outside a nested exit-frame portal (skip stencil
    DECR for isExit = true, use Equal stencil function when
    anyChildIsExit = true).
  • AR occlusion is disabled inside the portal interior for
    recursionLevel > 0 so virtual content is no longer discarded by
    depth-based occlusion in nested portals.

---

Compatibility

• Backward compatible with all existing single-pointer backends. iOS,
  AR (ARKit/ARCore), Cardboard, OVR, Daydream and Wasm continue to call the
  unchanged updateHitNode(camera, origin, ray) overload and observe no
  behavior change in hover / click / drag dispatch.

• Android 2025 ABI (16 KB-aligned .so files) requires Android
  Gradle Plugin 8.7+ in the consuming app. Minimum SDK unchanged.

• Meta Quest support requires the consuming app to register
  ReactViroPackage(ReactViroPackage.ViroPlatform.QUEST) in
  MainApplication.kt and declare the dual-Activity manifest entries
  (VRActivity, the com.oculus.intent.category.VR intent filter, Quest
  hardware features, hand-tracking and passthrough permissions). The Viro
  Expo plugin emits all of this automatically when xRMode includes
  "QUEST". Bare Android consumers will need to wire it manually.

---

Install path

Bare React Native is not tested for this release. ViroCore should work but
will require a substantial amount of manual wiring on the Android side
(VRActivity, manifest features, package registration in
MainApplication.kt) and iOS Podfile entries. For now we recommend
installing @reactvision/react-viro with the Expo Dev Client, where
the Viro Expo plugin emits all of the platform configuration
automatically. Bare RN support will be revisited in a follow-up release.