Repository navigation
v3.2.1
v3.2.1
Placed content stays put: every direct child of ViroARScene is anchored on iOS as it already was on Android, and on Android it now waits for tracking instead of giving up. Tracking no longer flickers on phones such as the Galaxy A56, cloud anchors host on a slow uplink, Android release builds with R8 pass, and an AR scene hidden by a tab switch no longer crashes on a queued call. Renderer binaries are rebuilt on virocore 3.2.1, with Spatial 1.5.0. The web build uses @reactvision/viro-web-renderer 1.1.1.
Everywhere
- A tap on a moving node fires
onClick. A node that moved during the press (an animation, physics, the camera) gotonClickStatebut noonClick. - A node faded by its parent's
opacityno longer hides translucent content behind it, such as text or another faded object.
iOS
- Content placed at the root of an AR scene stays put as ARKit refines its map. Each direct child of
ViroARSceneis anchored with an ARKit anchor once tracking is NORMAL, as on Android; itsposition, animations, drag and physics keep working in scene coordinates. Anchors, markers, planes andViroVPSAnchorare left alone. ViroARObjectMarkerfires when its object is detected, and an.arobjectthat fails to load is skipped with a warning instead of crashing the app.
Android
- Tracking no longer flickers on phones that could not sustain Viro's camera config (#568). The camera config is capped at 1920×1080 at 30 fps, a paused plane is kept instead of removed, and UNAVAILABLE reaches
onTrackingUpdatedafter about 200 ms. - A node at the root of an AR scene anchors once tracking starts, however long that takes; before, a slow start used up its three tries and it floated for the session.
- A release build with R8 minification passes: Viro's consumer rules ignore the classes the bundled GVR SDK references but does not ship.
- An AR scene method called while its screen is hidden answers
AR scene not availableinstead of crashing. - Hosting a cloud anchor with the
reactvisionprovider no longer fails on a slow uplink: the upload timeout grows with its size, up to 140 s (Spatial 1.5.0). - Content can follow a cloud anchor resolved with the
reactvisionprovider: the result is an ARCore anchor thatonAnchorUpdatedreports and<ViroARPlane anchorId>children follow.
Platform
- Cloud anchor resolve reports are accurate: real match and inlier counts, and why a resolve failed or was cancelled (Spatial 1.5.0).
Check when upgrading
- Android: a
reactvisionresolve result'sanchor.anchorIdis now the ARCore anchor's id;cloudAnchorIdis unchanged. An app that stored the oldanchorIdsees a different value. - Android: UNAVAILABLE from
onTrackingUpdatedarrives about 200 ms after tracking drops, not on the first frame. ViroARScene.createAnchoredNodereturns an anchor nothing can be attached to; to keep placed content in place, render it as a direct child ofViroARScene.