Skip to content

fix: report WebRTC initialization failures without probing - #88

Closed
thejustinwalsh wants to merge 6 commits into
NativeScript:mainfrom
thejustinwalsh:fix/xcode27
Closed

thejustinwalsh wants to merge 6 commits into
NativeScript:mainfrom
thejustinwalsh:fix/xcode27

Conversation

@thejustinwalsh

@thejustinwalsh thejustinwalsh commented Oct 1, 2026 •

Copy link
Copy Markdown

Opened this in error, I block WebRTC because it leaks my ip address, this confused the bots. I do think a WebTransport version would be nice.

Slop

Attempt the intended WebRTC connection directly, without creating and immediately closing a disposable capability-probe connection. If the real constructor throws, report the original initialization error and stop automatic reconnect attempts for that failure. Explicit reconnects remain possible; ordinary negotiation/network failures retain existing recovery behavior. AppShell retains its existing control WebSocket fallback; no video fallback or extension bypass is introduced.

The initial probe-based patch was replaced after browser comparison. In the affected Chrome session, the real connection still fails with RTCPeerConnection is not a constructor; the user reports a WebRTC privacy extension is installed. This PR improves error handling and does not claim to resolve that override. The user reports Safari and the ChatGPT side panel working.

Validation for commit 2918cd8:

  • Client TypeScript check passed.
  • Six targeted stream-client tests passed, including exactly one real constructor call with the requested configuration and preservation of an initialization failure.
  • Client production build passed and its assets were installed without restarting the native service.
  • Actual Chrome page showed the new specific initialization error rather than the generic unsupported-browser message.

The branch includes #87's Xcode framework-path prerequisite; this browser change is separate from that fix and should be rebased when #87 lands. No native HID ABI fix is included. Kept in draft pending final scope review and cross-browser verification of the latest build.

simonhamp and others added 2 commits September 16, 2026 18:45
Xcode 27 moved SimulatorKit.framework out of
Contents/Developer/Library/PrivateFrameworks and into
Contents/SharedFrameworks. The old directory is gone, so the display
bridge failed with "Unable to load SimulatorKit".

The bridge now reads the Xcode major version from version.plist next to
the developer directory. On 27 and later it tries SharedFrameworks first
and falls back to the old location. On older or unknown versions it
tries the old location first. If neither file exists it returns the
first candidate so the error still names the expected path.
@coderabbitai

coderabbitai Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on this repository. 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

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 73e7a314-7907-4d25-a0c4-727b20ed5752

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
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@thejustinwalsh
thejustinwalsh marked this pull request as draft October 1, 2026 14:49
@thejustinwalsh thejustinwalsh changed the title fix: preserve iOS touch input on touch-capable browsers fix: detect unusable browser WebRTC constructors Oct 1, 2026
@thejustinwalsh thejustinwalsh changed the title fix: detect unusable browser WebRTC constructors fix: report WebRTC initialization failures without probing Oct 1, 2026
@thejustinwalsh
thejustinwalsh deleted the fix/xcode27 branch October 1, 2026 15:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants