specs-debug

Check hand tracking by calling HandInputData.getInstance().getHand('right').isTracked() and logging the result. If it is always false, the Lens is running without a hand tracking provider, so guard the rest of your script with that check instead of asserting tracking.

Silent sync drops usually mean the writing client does not own the store. Log syncEntity.networkRoot.doIOwnStore() on the writing client; if it returns false, the property is written by a non-owner and discarded. Also verify mutations go through the SyncEntity API so onRemoteChange fires.

If onOpen never fires, the connection failed before the handshake, which almost always means Remote Service Gateway is not configured in project settings. A 401/403 in onError indicates a missing or expired gateway credential.

Confirm no child has a manual renderOrder, offset the content child +0.6 cm forward in Z, and set depthWrite = false on Component.Image. These issues are Canvas-sort or depth-flag bugs, not layout bugs; the full checklist lives in the specs-build-ui render-order rules.

A null output means the named output does not exist on the model, so re-check the model's output names. If the output exists but data length is zero, inference never ran; confirm runImmediate or runScheduled was called and the input tensor was populated.

Tracking drift is usually environmental: lighting below 100 LUX, repetitive visual patterns, moving objects, or thermal throttling all degrade VIO. Validate with the Point Cloud Lens on-device; if green points are plentiful but anchors still slip, investigate code causes like SyncKit ownership or world query timing.