There was an error while loading. Please reload this page.
ICE restart only ever worked on Blazor RTCOfferOptions.IceRestart is read by one binding. Blazor passes the options object to the browser's createOffer; Android, iOS, Mac Catalyst and Windows discard it, so the "restart" was a plain re-offer carrying the old credentials. The call renegotiated and nothing restarted, which is why a browser test passed it and this page said the feature was verified on all five. Fixed in the repository as of 26.9.21 by calling RestartIce() instead, so: - What works where says what each platform actually did, and gains a row for the automatic recovery, which is new. - Connection.md documents that a call now recovers by itself, and warns anyone on an earlier package that the button is decorative on four platforms. - The 26.9.18 release note carries a correction, because that is the published package and people are running it today.
Wiki: the seven stack pages One page per layer, bottom to top, each ending in a pointer to the next: WebRTCnative, Bindings, The unified API, Middleware, Connection and its two implementations, and the demo apps. The unified API page is named for what it is rather than for the package, because a sidebar with WebRTCme nested under WebRTCme reads as a mistake. Connection is split three ways. One page covering two topologies, two server deployments and two sequence diagrams would have been six hundred lines, and the two implementations have almost nothing in common below IConnection. Twelve mermaid diagrams, all parsed and rendered under the strict security level GitHub uses before being committed. Mermaid rather than SVG pairs: it themes itself for dark mode and stays editable in place. Connection-Signaling records that the server's tracked appsettings.json carries a real Xirsys credential, because a reader who forks this needs to know not to rely on it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>