NVIDIA / NVIDIA/cloudxr-framework
CloudXRKit 6.2.0 fails locally with 0x800B1004 (NVST_R_INVALID_VALUE) on visionOS 26.5 / 27.0 — no network traffic emitted
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 31
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Environment: cloudxr-framework 6.2.0 (latest release) + cloudxr-apple-generic-viewer (unmodified, manual-IP mode); Apple Vision Pro ×2 (visionOS 26.5 build 23O471, visionOS 27.0 beta 24M5306i); servers tested: CloudXR Runtime 6.2.1 on both Ubuntu 24.04 (RTX 5090, driver 580.159.03) and Windows 11 (RTX 5070 Laptop, driver 592.19).
Symptom: session.connect() with .local(ip:) fails in ~1.1s with Error Domain=NVIDIAStreamKit Code=2148208644 "0x800B1004" UserInfo={SessionNotificationType=51}. Bifrost log stops after nvbCreateClient/nvbSetHttpClient. Packet capture on the server confirms zero packets are ever sent — the failure is entirely client-local, before any network I/O.
Ruled out: server platform (identical on Linux & Windows servers), device (2 devices), OS version (26.5 & 27.0), Local Network permission (granted), ATS (LAN-exempt), network environment (office Wi-Fi & cellular hotspot), server reachability (port 48010 verified open).
Note: the same devices stream successfully via the visionOS 26.4 FoveatedStreaming system path against a Windows server (Runtime 6.2.1 + Stream Manager 6.1.0 + StreamingSession sample), so the device-side system stack is healthy. The public framework's docs/deployment targets still reference visionOS 2.4 / Xcode 16.4 — is a visionOS 26.x-compatible framework release planned? This is blocking Linux-server deployments (which per the LÖVR sample docs are supported with the native AVP client).
Secondary request: Stream Manager (client-auth/token issuance) is Windows-only, which also blocks the FoveatedStreaming path on Linux servers. A Linux Stream Manager build or a documented token-issuance API would unblock this.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the unmodified cloudxr-apple-generic-viewer and its session.connect(.local(ip:)) entry point, then review the Bifrost log around nvbCreateClient and nvbSetHttpClient. Compare the client-local failure with the successful visionOS 26.4 FoveatedStreaming path; done means confirming framework compatibility or documenting a supported visionOS 26.x and Linux-server path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, swift
- Domain
- mobile-dev, networking
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100