[yanziz-nvidia]

Desktop Chrome can show a green Connect button after the emulator fallback reports success, then reject requestSession with “No XR hardware found” when the native XR runtime remains active.

Update IWER and DevUI to 2.7.0 with matching CDN integrity hashes and align the IWER development dependency. After forcing fallback installation, verify immersive session support before reporting readiness or exposing the emulated device. Preserve retry after failure and the release branch’s browser-test readiness log.

Validation:

• Four loader regression tests pass, including skipped installation and subsequent retry.
• Targeted ESLint and Prettier checks pass.
• Full repository pre-commit checks pass (SKIP=check-copyright-year).
• Clean isolated installation of iwer@^2.7.0 succeeds.
• Headless Chrome with native XR present but no hardware starts emulated VR and AR sessions using both actual 2.7.0 CDN bundles; both integrity hashes verified.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: NVIDIA/IsaacCapture
• Branch: release/1.6.x
• File: .coderabbit.yaml
• Commit: b13bbb4
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Enterprise
• Run ID: 510e8954-6cce-464b-aedb-830275658b80

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}