Skip to content

fix: WebSocket binaryType handling — stop unconditional Blob interception of binary messages - #16173

Merged
Julio César Rocha (JunielKatarn) merged 10 commits into
microsoft:mainfrom
Virtual-Fulfillment-Technologies-Inc:vendora/fix-websockets
Jun 7, 2026
Merged

fix: WebSocket binaryType handling — stop unconditional Blob interception of binary messages#16173
Julio César Rocha (JunielKatarn) merged 10 commits into
microsoft:mainfrom
Virtual-Fulfillment-Technologies-Inc:vendora/fix-websockets

Conversation

@gmacmaster

@gmacmaster Gordon MacMaster (gmacmaster) commented May 22, 2026

Copy link
Copy Markdown
Contributor

Description

WebSocket binaryType = 'arraybuffer' is silently broken on React Native Windows.

Type of Change

Bug fix (non-breaking change which fixes an issue)

Why

WebSocket binaryType = 'arraybuffer' is silently broken on React Native Windows. All binary WebSocket messages are unconditionally intercepted by BlobWebSocketModuleContentHandler and converted to Blobs, regardless of whether the socket has been registered for blob handling via addWebSocketHandler. This means:

Setting binaryType = 'arraybuffer' has no effect — binary messages still arrive as Blobs
The JavaScript-side WebSocket.js never executes its base64-to-ArrayBuffer conversion path for binary messages
Applications relying on ArrayBuffer delivery (e.g., PowerSync, binary protocol clients) are forced to implement custom Blob-to-ArrayBuffer conversion patches
This diverges from the behavior on iOS and Android, where binaryType correctly controls binary message delivery format.

What

The root cause is in DefaultBlobResource.cpp: IBlobResource::Make() unconditionally registers a BlobWebSocketModuleContentHandler on the ReactContext property bag, and WebSocketModule.cpp routes all binary messages through it without checking whether the specific socket was registered via addWebSocketHandler.

The BlobWebSocketModuleContentHandler already tracks registered socket IDs in m_socketIds (populated by Register/Unregister), but this set was never consulted during message processing.

Changes across 4 files:

IWebSocketModuleContentHandler.h — Changed both ProcessMessage overloads from void to bool return type. true = message was handled by the content handler; false = caller should fall back to default delivery.

DefaultBlobResource.h — Updated BlobWebSocketModuleContentHandler::ProcessMessage signatures to return bool.

DefaultBlobResource.cpp — Both ProcessMessage overloads now read the socket ID from params["id"], acquire m_mutex, and check m_socketIds. If the socket is not registered, they return false without processing. This check is atomic with the message processing, avoiding any TOCTOU gap between a separate Supports() check and ProcessMessage.

WebSocketModule.cpp — The SetOnMessage callback now checks the bool return value from ProcessMessage. If false, it falls through to the default path (args["data"] = message), which delivers the base64-encoded binary data to JavaScript where WebSocket.js decodes it to an ArrayBuffer.

Behavior after the fix:

binaryType = 'blob' (socket registered via addWebSocketHandler) — binary messages delivered as Blobs, same as before.
binaryType = 'arraybuffer' or default (socket not registered) — binary messages delivered as ArrayBuffer via the standard JS-side base64 decode path.
Screenshots
N/A — this is a data-path fix with no UI changes. Verified by observing WebSocket message delivery type in application-level diagnostics.

Testing

Verified end-to-end on a Windows device running a React Native application with PowerSync (real-time sync over binary WebSocket):

Before fix: All binary messages hit Blob conversion path (fileReader branch in application diagnostic stats), binaryType = 'arraybuffer' caused silent message drops.
After fix: All binary messages hit the passthrough/ArrayBuffer path (passthrough branch active, fileReader: 0), no message drops.
Tested both binaryType modes:

'arraybuffer' — messages arrive as ArrayBuffer in MessageEvent.data (was broken, now works)
'blob' — messages arrive as Blob in MessageEvent.data (still works, no regression)

Changelog

Should this change be included in the release notes: yes

Fix WebSocket binaryType handling on Windows — binary messages are no longer unconditionally converted to Blobs. Sockets using binaryType = 'arraybuffer' (the standard default) now correctly receive ArrayBuffer data.

Microsoft Reviewers: Open in CodeFlow

* blob support

* pr comments

* pr comments

* Update DefaultBlobResource.cpp
@JunielKatarn

Copy link
Copy Markdown
Contributor

@microsoft/jshost allow me to review before approving.

@gmacmaster

Copy link
Copy Markdown
Contributor Author

Julio César Rocha (@JunielKatarn) have you had a chance to review?

@JunielKatarn

Copy link
Copy Markdown
Contributor

Beginning review.

@JunielKatarn

Copy link
Copy Markdown
Contributor

I have submitted a PR to your branch adding a test for this use case which will eventually be part of our automation.
Virtual-Fulfillment-Technologies-Inc#9
Feel free to adapt or improve if it doesn't properly test your change.

The change looks correct.
I only have feedback on where part of the implementation takes place and perhaps some naming convention.
I will add those specifics directly on the files section.

Comment thread vnext/Shared/Modules/IWebSocketModuleContentHandler.h Outdated
Comment thread vnext/Shared/Modules/IWebSocketModuleContentHandler.h Outdated
Comment thread vnext/Shared/Modules/WebSocketModule.cpp
@microsoft-github-policy-service microsoft-github-policy-service Bot added the Needs: Author Feedback The issue/PR needs activity from its author (label drives bot activity) label May 31, 2026
@microsoft-github-policy-service microsoft-github-policy-service Bot removed the Needs: Author Feedback The issue/PR needs activity from its author (label drives bot activity) label Jun 1, 2026
* Add WebSocketArrayBuffer headless test

* Skip test by default
@gmacmaster
Gordon MacMaster (gmacmaster) requested a review from a team as a code owner June 1, 2026 03:00
@gmacmaster

Copy link
Copy Markdown
Contributor Author

Julio César Rocha (@JunielKatarn) Comments addressed

@github-actions

github-actions Bot commented Jun 2, 2026

Copy link
Copy Markdown

Performance Test Results

Branch: vendora/fix-websockets
Commit: 1260fbc4
Time: 2026-06-05T23:34:12.681Z
Tests: 161/161 passed

✅ Passed

161 scenario(s) across 28 suite(s) — no regressions

SectionList

Scenario Mean Median StdDev Renders vs Baseline
SectionList mount 2.60ms 2.00ms ±1.65ms 1 -60.0%
SectionList unmount 0.20ms 0.00ms ±0.42ms 0 +0.0%
SectionList rerender 6.20ms 6.00ms ±1.75ms 2 -42.9%
SectionList with-3-sections-15-items 3.00ms 3.00ms ±0.67ms 1 -45.5%
SectionList with-5-sections-50-items 3.10ms 3.00ms ±1.52ms 1 -50.0%
SectionList with-10-sections-200-items 2.40ms 2.00ms ±0.52ms 1 -63.6%
SectionList with-20-sections-200-items 2.60ms 2.00ms ±1.35ms 1 -60.0%
SectionList with-section-separator 1.10ms 1.00ms ±0.32ms 1 -50.0%
SectionList with-item-separator 1.60ms 1.00ms ±1.26ms 1 -50.0%
SectionList with-header-footer 1.00ms 1.00ms ±0.00ms 1 -50.0%
SectionList with-section-footer 1.20ms 1.00ms ±1.40ms 1 -50.0%
SectionList with-sticky-section-headers 1.00ms 1.00ms ±0.00ms 1 -50.0%
SectionList with-empty-list 0.20ms 0.00ms ±0.42ms 1 -100.0%
SectionList with-50-sections-1000-items 0.80ms 1.00ms ±0.42ms 1 -50.0%

FlatList

Scenario Mean Median StdDev Renders vs Baseline
FlatList mount 2.50ms 2.50ms ±0.53ms 1 -37.5%
FlatList unmount 0.00ms 0.00ms ±0.00ms 0 +0.0%
FlatList rerender 5.50ms 5.00ms ±1.78ms 2 -44.4%
FlatList with-10-items 2.30ms 2.00ms ±0.48ms 1 -50.0%
FlatList with-100-items 3.10ms 3.00ms ±1.20ms 1 -40.0%
FlatList with-500-items 2.50ms 2.50ms ±0.53ms 1 -37.5%
FlatList with-1000-items 2.70ms 2.00ms ±1.25ms 1 -50.0%
FlatList horizontal 2.40ms 3.00ms ±0.97ms 1 -40.0%
FlatList with-separator 1.00ms 1.00ms ±0.00ms 1 -50.0%
FlatList with-header-footer 0.80ms 1.00ms ±0.42ms 1 -50.0%
FlatList with-empty-list 0.10ms 0.00ms ±0.32ms 1 -100.0%
FlatList with-get-item-layout 1.40ms 1.00ms ±1.26ms 1 +0.0%
FlatList inverted 0.70ms 1.00ms ±0.48ms 1 -33.3%
FlatList with-num-columns 1.30ms 1.00ms ±0.48ms 1 -66.7%

TouchableOpacity

Scenario Mean Median StdDev Renders vs Baseline
TouchableOpacity mount 0.60ms 1.00ms ±0.52ms 1 +0.0%
TouchableOpacity unmount 0.10ms 0.00ms ±0.32ms 0 +0.0%
TouchableOpacity rerender 0.60ms 0.00ms ±1.26ms 2 -100.0%
TouchableOpacity custom-active-opacity 0.40ms 0.00ms ±0.52ms 1 -100.0%
TouchableOpacity disabled 0.20ms 0.00ms ±0.42ms 1 -100.0%
TouchableOpacity with-all-handlers 0.30ms 0.00ms ±0.48ms 1 -100.0%
TouchableOpacity with-hit-slop 0.60ms 1.00ms ±0.52ms 1 +0.0%
TouchableOpacity with-delay 0.40ms 0.00ms ±0.52ms 1 -100.0%
TouchableOpacity nested 0.60ms 1.00ms ±0.52ms 1 +0.0%
TouchableOpacity multiple-10 3.13ms 3.00ms ±1.68ms 1 -50.0%
TouchableOpacity multiple-50 13.07ms 12.00ms ±2.49ms 1 -58.6%
TouchableOpacity multiple-100 10.87ms 10.00ms ±2.42ms 1 -80.0%

ScrollView

Scenario Mean Median StdDev Renders vs Baseline
ScrollView mount 0.20ms 0.00ms ±0.42ms 1 +0.0%
ScrollView unmount 0.00ms 0.00ms ±0.00ms 0 +0.0%
ScrollView rerender 0.30ms 0.00ms ±0.48ms 2 -100.0%
ScrollView children-20 1.67ms 2.00ms ±0.49ms 1 -50.0%
ScrollView children-100 9.27ms 9.00ms ±1.28ms 1 -43.8%
ScrollView horizontal 1.90ms 2.00ms ±0.57ms 1 -50.0%
ScrollView sticky-headers 1.90ms 2.00ms ±1.20ms 1 -33.3%
ScrollView scroll-indicators 0.30ms 0.00ms ±0.48ms 1 -100.0%
ScrollView nested 0.80ms 1.00ms ±0.63ms 1 +0.0%
ScrollView content-container-style 0.40ms 0.00ms ±0.52ms 1 -100.0%
ScrollView children-500 12.40ms 12.00ms ±3.04ms 1 -36.8%

TouchableHighlight

Scenario Mean Median StdDev Renders vs Baseline
TouchableHighlight mount 0.20ms 0.00ms ±0.42ms 1 -100.0%
TouchableHighlight unmount 0.00ms 0.00ms ±0.00ms 0 +0.0%
TouchableHighlight rerender 0.20ms 0.00ms ±0.42ms 2 -100.0%
TouchableHighlight custom-underlay-color 0.60ms 0.00ms ±1.26ms 1 +0.0%
TouchableHighlight custom-active-opacity 0.20ms 0.00ms ±0.42ms 1 +0.0%
TouchableHighlight disabled 0.20ms 0.00ms ±0.42ms 1 +0.0%
TouchableHighlight with-all-handlers 0.20ms 0.00ms ±0.42ms 1 +0.0%
TouchableHighlight with-hit-slop 0.20ms 0.00ms ±0.42ms 1 +0.0%
TouchableHighlight nested-touchables 0.30ms 0.00ms ±0.48ms 1 -100.0%
TouchableHighlight multiple-touchables-10 1.10ms 1.00ms ±0.32ms 1 -66.7%
TouchableHighlight multiple-touchables-50 7.10ms 7.00ms ±1.79ms 1 -44.0%
TouchableHighlight multiple-touchables-100 13.30ms 13.50ms ±1.25ms 1 -40.0%

Pressable

Scenario Mean Median StdDev Renders vs Baseline
Pressable mount 0.10ms 0.00ms ±0.32ms 1 +0.0%
Pressable unmount 0.00ms 0.00ms ±0.00ms 0 +0.0%
Pressable rerender 0.40ms 0.00ms ±0.52ms 2 -100.0%
Pressable with-all-handlers 0.10ms 0.00ms ±0.32ms 1 +0.0%
Pressable with-style-function 0.10ms 0.00ms ±0.32ms 1 +0.0%
Pressable disabled 0.20ms 0.00ms ±0.42ms 1 +0.0%
Pressable with-hit-slop 0.10ms 0.00ms ±0.32ms 1 +0.0%
Pressable nested 0.30ms 0.00ms ±0.48ms 1 -100.0%
Pressable multiple-10 1.67ms 1.00ms ±1.29ms 1 -66.7%
Pressable multiple-50 8.13ms 7.00ms ±1.96ms 1 -50.0%
Pressable multiple-100 9.93ms 9.00ms ±5.73ms 1 -25.0%

Modal

Scenario Mean Median StdDev Renders vs Baseline
Modal mount 0.20ms 0.00ms ±0.42ms 1 +0.0%
Modal unmount 0.00ms 0.00ms ±0.00ms 0 +0.0%
Modal rerender 0.30ms 0.00ms ±0.48ms 2 +0.0%
Modal slide-animation 0.10ms 0.00ms ±0.32ms 1 +0.0%
Modal fade-animation 0.20ms 0.00ms ±0.42ms 1 +0.0%
Modal transparent 0.20ms 0.00ms ±0.42ms 1 +0.0%
Modal with-callbacks 0.10ms 0.00ms ±0.32ms 1 +0.0%
Modal rich-content 0.90ms 1.00ms ±0.32ms 1 -50.0%
Modal with-accessibility 0.10ms 0.00ms ±0.32ms 1 +0.0%

Image

Scenario Mean Median StdDev Renders vs Baseline
Image mount 0.10ms 0.00ms ±0.32ms 1 +0.0%
Image unmount 0.00ms 0.00ms ±0.00ms 0 +0.0%
Image rerender 0.20ms 0.00ms ±0.42ms 2 +0.0%
Image with-resize-mode 0.10ms 0.00ms ±0.32ms 1 +0.0%
Image with-border-radius 0.10ms 0.00ms ±0.32ms 1 +0.0%
Image with-tint-color 0.10ms 0.00ms ±0.32ms 1 +0.0%
Image with-blur-radius 0.10ms 0.00ms ±0.32ms 1 +0.0%
Image with-accessibility 0.40ms 0.00ms ±1.26ms 1 +0.0%
Image multiple-10 0.47ms 0.00ms ±0.52ms 1 -100.0%
Image multiple-50 1.93ms 2.00ms ±0.26ms 1 -33.3%
Image multiple-100 4.73ms 4.00ms ±1.16ms 1 -50.0%

ActivityIndicator

Scenario Mean Median StdDev Renders vs Baseline
ActivityIndicator mount 0.10ms 0.00ms ±0.32ms 1 +0.0%
ActivityIndicator unmount 0.00ms 0.00ms ±0.00ms 0 +0.0%
ActivityIndicator rerender 0.10ms 0.00ms ±0.32ms 2 +0.0%
ActivityIndicator size-large 0.10ms 0.00ms ±0.32ms 1 +0.0%
ActivityIndicator size-small 0.10ms 0.00ms ±0.32ms 1 +0.0%
ActivityIndicator with-color 0.10ms 0.00ms ±0.32ms 1 +0.0%
ActivityIndicator not-animating 0.10ms 0.00ms ±0.32ms 1 +0.0%
ActivityIndicator with-accessibility 0.10ms 0.00ms ±0.32ms 1 +0.0%
ActivityIndicator multiple-10 0.47ms 0.00ms ±0.52ms 1 -100.0%
ActivityIndicator multiple-50 2.07ms 2.00ms ±0.26ms 1 -50.0%
ActivityIndicator multiple-100 4.40ms 4.00ms ±0.91ms 1 -42.9%

Switch

Scenario Mean Median StdDev Renders vs Baseline
Switch mount 0.10ms 0.00ms ±0.32ms 1 +0.0%
Switch unmount 0.10ms 0.00ms ±0.32ms 0 +0.0%
Switch rerender 0.30ms 0.00ms ±0.48ms 2 -100.0%
Switch value-true 0.10ms 0.00ms ±0.32ms 1 +0.0%
Switch disabled 0.10ms 0.00ms ±0.32ms 1 +0.0%
Switch custom-colors 0.10ms 0.00ms ±0.32ms 1 +0.0%
Switch on-value-change 0.10ms 0.00ms ±0.32ms 1 +0.0%
Switch with-accessibility 0.10ms 0.00ms ±0.32ms 1 +0.0%
Switch multiple-10 0.87ms 1.00ms ±0.35ms 1 -50.0%
Switch multiple-50 5.33ms 4.00ms ±2.32ms 1 -55.6%
Switch multiple-100 9.53ms 9.00ms ±2.45ms 1 -43.8%

Button

Scenario Mean Median StdDev Renders vs Baseline
Button mount 0.30ms 0.00ms ±0.48ms 1 -100.0%
Button unmount 0.00ms 0.00ms ±0.00ms 0 +0.0%
Button rerender 0.90ms 1.00ms ±1.20ms 2 +0.0%
Button disabled 0.30ms 0.00ms ±0.48ms 1 -100.0%
Button with-color 0.30ms 0.00ms ±0.48ms 1 -100.0%
Button with-accessibility 0.20ms 0.00ms ±0.42ms 1 -100.0%
Button multiple-10 3.13ms 3.00ms ±1.19ms 1 -50.0%
Button multiple-50 11.20ms 13.00ms ±4.59ms 1 -51.9%
Button multiple-100 8.27ms 8.00ms ±1.71ms 1 -57.9%

TextInput

Scenario Mean Median StdDev Renders vs Baseline
TextInput mount 0.10ms 0.00ms ±0.32ms 1 +0.0%
TextInput unmount 0.00ms 0.00ms ±0.00ms 0 +0.0%
TextInput rerender 0.20ms 0.00ms ±0.42ms 2 +0.0%
TextInput multiline 0.10ms 0.00ms ±0.32ms 1 +0.0%
TextInput with-value 0.10ms 0.00ms ±0.32ms 1 +0.0%
TextInput styled 0.00ms 0.00ms ±0.00ms 1 +0.0%
TextInput multiple-100 4.20ms 4.00ms ±1.15ms 1 -42.9%

View

Scenario Mean Median StdDev Renders vs Baseline
View mount 0.10ms 0.00ms ±0.32ms 1 +0.0%
View unmount 0.00ms 0.00ms ±0.00ms 0 +0.0%
View rerender 0.10ms 0.00ms ±0.32ms 2 +0.0%
View nested-50 2.07ms 2.00ms ±1.22ms 1 -33.3%
View nested-100 4.33ms 4.00ms ±1.40ms 1 -42.9%
View shadow 0.10ms 0.00ms ±0.32ms 1 +0.0%
View border-radius 0.10ms 0.00ms ±0.32ms 1 +0.0%
View nested-500 10.47ms 7.00ms ±7.55ms 1 -30.0%

Text

Scenario Mean Median StdDev Renders vs Baseline
Text mount 0.10ms 0.00ms ±0.32ms 1 +0.0%
Text unmount 0.00ms 0.00ms ±0.00ms 0 +0.0%
Text rerender 0.40ms 0.00ms ±1.26ms 2 +0.0%
Text long-1000 0.10ms 0.00ms ±0.32ms 1 +0.0%
Text nested 0.10ms 0.00ms ±0.32ms 1 +0.0%
Text styled 0.10ms 0.00ms ±0.32ms 1 +0.0%
Text multiple-100 4.87ms 5.00ms ±1.13ms 1 -28.6%

SectionList.native-perf-test.ts

Scenario Mean Median StdDev Renders vs Baseline
SectionList native mount 2.96ms 2.79ms ±0.45ms 1 -57.1%

FlatList.native-perf-test.ts

Scenario Mean Median StdDev Renders vs Baseline
FlatList native mount 3.66ms 3.20ms ±1.32ms 1 -65.3%

TouchableHighlight.native-perf-test.ts

Scenario Mean Median StdDev Renders vs Baseline
TouchableHighlight native mount 0.93ms 0.90ms ±0.19ms 1 -57.0%

TouchableOpacity.native-perf-test.ts

Scenario Mean Median StdDev Renders vs Baseline
TouchableOpacity native mount 1.13ms 1.07ms ±0.17ms 1 -65.9%

Pressable.native-perf-test.ts

Scenario Mean Median StdDev Renders vs Baseline
Pressable native mount 0.90ms 0.89ms ±0.10ms 1 -64.4%

ScrollView.native-perf-test.ts

Scenario Mean Median StdDev Renders vs Baseline
ScrollView native mount 2.26ms 2.22ms ±0.27ms 1 -45.2%

ActivityIndicator.native-perf-test.ts

Scenario Mean Median StdDev Renders vs Baseline
ActivityIndicator native mount 1.22ms 1.12ms ±0.31ms 1 -54.7%

TextInput.native-perf-test.ts

Scenario Mean Median StdDev Renders vs Baseline
TextInput native mount 1.67ms 1.40ms ±0.70ms 1 -65.8%

Switch.native-perf-test.ts

Scenario Mean Median StdDev Renders vs Baseline
Switch native mount 0.70ms 0.62ms ±0.24ms 1 -64.4%

Button.native-perf-test.ts

Scenario Mean Median StdDev Renders vs Baseline
Button native mount 1.05ms 1.03ms ±0.12ms 1 -60.4%

Modal.native-perf-test.ts

Scenario Mean Median StdDev Renders vs Baseline
Modal native mount 0.74ms 0.48ms ±0.66ms 1 -60.5%

Image.native-perf-test.ts

Scenario Mean Median StdDev Renders vs Baseline
Image native mount 1.58ms 1.36ms ±0.74ms 1 -39.7%

View.native-perf-test.ts

Scenario Mean Median StdDev Renders vs Baseline
View native mount 0.57ms 0.52ms ±0.15ms 1 -63.8%

Text.native-perf-test.ts

Scenario Mean Median StdDev Renders vs Baseline
Text native mount 0.75ms 0.71ms ±0.10ms 1 -59.1%

@acoates-ms

Copy link
Copy Markdown
Contributor

/azp run

@azure-pipelines

Copy link
Copy Markdown
Contributor
Azure Pipelines successfully started running 1 pipeline(s).

@gmacmaster

Copy link
Copy Markdown
Contributor Author

Andrew Coates (@acoates-ms) these are just the random failures right? Just needs a rerun?

@JunielKatarn

Copy link
Copy Markdown
Contributor

Andrew Coates (@acoates-ms) these are just the random failures right? Just needs a rerun?

Looks like it.
However, a JavaScript validation (yarn lint) also failed.
This is most likely a missing registration for the JavaScript test.
I'll look into it and propose a change.

@JunielKatarn

Copy link
Copy Markdown
Contributor

@gmacmaster

Copy link
Copy Markdown
Contributor Author

See Virtual-Fulfillment-Technologies-Inc#10

Merged

@JunielKatarn

Copy link
Copy Markdown
Contributor

/azp run

@azure-pipelines

Copy link
Copy Markdown
Contributor
Azure Pipelines successfully started running 1 pipeline(s).

@JunielKatarn

Copy link
Copy Markdown
Contributor

Failing validation is due unrelated changes after the build image upgrade.
Please pull the latest main. Almost ready to merge.

@gmacmaster

Copy link
Copy Markdown
Contributor Author

Failing validation is due unrelated changes after the build image upgrade. Please pull the latest main. Almost ready to merge.

Just pulled

@JunielKatarn

Copy link
Copy Markdown
Contributor

/azp run

@azure-pipelines

Copy link
Copy Markdown
Contributor
Azure Pipelines successfully started running 1 pipeline(s).

@JunielKatarn
Julio César Rocha (JunielKatarn) merged commit 5be8c05 into microsoft:main Jun 7, 2026
32 of 33 checks passed
Julio César Rocha (JunielKatarn) added a commit that referenced this pull request Jun 10, 2026
* Upgrade to PowerShell 7 (#16075)

* Ran NuGetRestoreForceEvaluateAllSolutions.ps1

* Define installNuGetPackages task; Install pwsh 7.6.1

* Replace powershell.exe with pwsh.exe

* Change files

* CI: Ensure NuGet is availabe before `yarn install`

* Add NuGetAuthenticate before yarn install

* Do not download PowerShell on CI/CD environments

* Fix just-task JS syntax

* Add dotnet-tools manifest

* Fix pwsh.exe tool path

* Resolve dotnet-tools.json path

* Use dotnet for `nuget locals`

* Use PWSH in nuget-restore-task.js

* Break dependency loop in just-task

* Update other ADO tasks

* Update @react-native-windows/automation

* Rename findPwsh as findPowerShell

* Drop powershell export from commandWithProgress

* Change files

* Add README for find-dotnet-tools

* Add README to package.json

* Adjust newline

* Run task `installDotnetTools` only when not in CI

* Install .NET tools in CI

* Install .NET on prepare-js-env

* Do not install .NET tools on CI

* Quote powershell path

* fix yarn lint

* Ran NuGetRestoreForceEvaluateAllSolutions.ps1

* Restore deleted lock files

* Add missing dependency

* Use -Command for compatible PWSH calls

* Use -Command pwsh argument

* Correct runPowerShellScriptFunction cmd escaping

* Quote pwsh command in runPowerShellScriptFunction

* Remove quotes

* Quote remaining findPowerShell() calls for execSync

* Add temporary diagnostic commands

* Diagnostics

* Diagnostics

* Diagnostics

* Add runPowerShellScriptFunction argument to delegate Appx-related commands to Windows PowerShell

* Remove diagnostics steps

* Use execFileSync instead of execSync in deploy.ts

* Remove querystrings from FS paths

* Suppress warning when using `-UseWindowsPowerShell`

* Revert "Remove querystrings from FS paths"

This reverts commit e1f3cfd.

* Use pipe semantics for Get-AppxPackage in resolveAppName

* Hard-fail if PowerShell 7 cannot be found.

Do not fall back to Windows PowerShell (powershell.exe).
PowerShell code may not be backwards compatible.

* Improve missing pwsh.exe error message

* Add package resolution pipeline test

* UseWindowsPowerShell for package resolution test

* Try to read package Microsoft.PrintDialog

* Replace stderr redirection with -WarningAction

* Replace stderr redirection with -WarningAction

* Print sample app names on appWindow error

* Add more diagnostics

* Add missing -WarningAction SilentlyContinue

* Revert "Add more diagnostics"

This reverts commit 8c10bc4.

* Revert "Print sample app names on appWindow error"

This reverts commit 6e70148.

* Remove CI probing tasks

* Revert "Use pipe semantics for Get-AppxPackage in resolveAppName"

This reverts commit 6c46c73.

Co-authored-by: Copilot <copilot@github.com>

* Remove unused escaping logic

* Re-introduce deleted .lock.json

---------

Co-authored-by: Copilot <copilot@github.com>

* Fix PowerShell installation (#16164)

* Defer findPowershell to layoutMSRNCxx

* Change files

* Upgrade to Visual Studio 2026 (#16170)

* Update deps script. TODO: test

* Upgrade rnw-deps to .NET 10

* Defer findPowershell to layoutMSRNCxx

* Upgrade VS version to 18.6.1

* Drop /async in MSVC 14.5

* Replace std::future coroutines with WinRT types

* clang format

* Change files

* Drop Windows10SDK.19041

* Change files

* Set TargetFramework to net10.0-windows10.0.26100.0

* Use IAsyncOperation instead of out parameters

* Install .NET 10

* Revert "Install .NET 10"

This reverts commit 5f75dc0.

* Revert "Set TargetFramework to net10.0-windows10.0.26100.0"

This reverts commit 22a4791.

* clang format

* Upgrade CsWinRT.csproj to .NET 8

* Fix filters

* Upgrade MSRN SLN to VS 18

* Revert parameter signature in LoadBundleAsync

* Update CSWinRT lock

* Allow all versions of VS 2026

* Use IBuffer instead of hstring as payload

GetJavaScriptFromServerAsync retuns bundle contents as hstring (16 bit)
It then gets converted to an 8-bit string. This conversion drops
bytes consideres "invalid". Those bytes are expected as part of the Hermes bundle header.

Transmitting the bundle as an IBuffer preserves the original bytes and avoids the conversion issues.

* Potential fix for pull request finding

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

* Use WinRT exception types instead of std

---------

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

* Upgrade to GoogleTest Adapter 1.8.1.8 (#16218)

* Upgrade to GoogleTest adapter 1.8.1.8

* Change files

* Update package lock files

* Upgrade CI agents to Windows Server 2025 (#16208)

* Use image rnw-img-vs2026-node24

* Update fork-sync/bin.js chmod

* Upgrade to MSVC 14.5

* Drop -UseWindowsPowerShell fallback

* Manually install yarn

* Upgrade to .NET Hosting Bundle 10.0.8

* Change files

* Fix change file

* Add temp npm install yarn in templates

* Test yarn location

* update

* update

* TEMPORARILY revert agent image

* Print yarn version in setup

* Revert "TEMPORARILY revert agent image"

This reverts commit 7c175e1.

* update

* update

* update

* Upgrade to msbuildVersion: 18.0

* Update Google test adapter location

* Remove unused statement

* Remove probing tasks

* Upgrade to VSTest@3

* Upgrade more projects and scripts to VS 2026

* Explicitly set vstest.console location

* Install midgard-yarn and verdaccio in-place

* Fix yarn version

* Update node-tests version

* Use pwsh in Add-AppDevPackage

* Make WindowsStoreAppUtils use PowerShell 7

* Update snapshot values

* Update snapshot from failing x86 run

* Use the --tag argument for verdaccio under Node 24

* Ignore/warn on unstable click test

* Enable WMIC for RN Doctor

* Disable RN doctor until it drops WMIC

* Add rnw-img-vs2026-node24.json (#16224)

* Update CI verdaccio to 6.7.2 (#16223)

* Upgrade to Microsoft.WindowsAppSDK 1.8.260508005 (#16225)

* Upgrade to Microsoft.WindowsAppSDK 1.8.260508005

* Change files

* fix: WebSocket binaryType handling — stop unconditional Blob interception of binary messages (#16173)

* blob support (#8)

* blob support

* pr comments

* pr comments

* Update DefaultBlobResource.cpp

* Create react-native-windows-c3827e14-777b-475a-bf00-dc169bf89f3d.json

* Add WebSocketArrayBuffer headless test (#9)

* Add WebSocketArrayBuffer headless test

* Skip test by default

* pr comments

* Update overrides (#10)

---------

Co-authored-by: Julio César Rocha <JunielKatarn@users.noreply.github.com>

* Upgrade projects to .NET 10 (#16226)

* Upgrade projects to .NET 10

* Upgrade lock files

* Change files

* Fix missing conflicts

* Update packages lock

* Remove extra yarn step

* Re-introduce JS Desktop integration tests (#16228)

* Remove redundant condition Desktop.IntegrationTests.SkipRNTester

Modify Desktop.IntegrationTests.Filter instead.

* Re-introduce WebSocket and WebSocketBlob tests

* Make WSBlob test compare contents

* Rename method to RunTest

* Handle initial message from default endpoint

* Change files

* Migrate XHR test

* Port Fetch test

* Port Blob test

* WebSocketMultipleSendTest

* Remove JS WebSocket servers

* Skip in CI for now

* Remove ban-types

* Fix DynamicReaderWriterTests

* Use WinRT coroutine types for UwpScriptStore

* clang format

---------

Co-authored-by: Copilot <copilot@github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Gordon MacMaster <31481849+gmacmaster@users.noreply.github.com>
Julio César Rocha (JunielKatarn) added a commit that referenced this pull request Jun 12, 2026
* Upgrade to PowerShell 7 (#16075)

* Ran NuGetRestoreForceEvaluateAllSolutions.ps1

* Define installNuGetPackages task; Install pwsh 7.6.1

* Replace powershell.exe with pwsh.exe

* Change files

* CI: Ensure NuGet is availabe before `yarn install`

* Add NuGetAuthenticate before yarn install

* Do not download PowerShell on CI/CD environments

* Fix just-task JS syntax

* Add dotnet-tools manifest

* Fix pwsh.exe tool path

* Resolve dotnet-tools.json path

* Use dotnet for `nuget locals`

* Use PWSH in nuget-restore-task.js

* Break dependency loop in just-task

* Update other ADO tasks

* Update @react-native-windows/automation

* Rename findPwsh as findPowerShell

* Drop powershell export from commandWithProgress

* Change files

* Add README for find-dotnet-tools

* Add README to package.json

* Adjust newline

* Run task `installDotnetTools` only when not in CI

* Install .NET tools in CI

* Install .NET on prepare-js-env

* Do not install .NET tools on CI

* Quote powershell path

* fix yarn lint

* Ran NuGetRestoreForceEvaluateAllSolutions.ps1

* Restore deleted lock files

* Add missing dependency

* Use -Command for compatible PWSH calls

* Use -Command pwsh argument

* Correct runPowerShellScriptFunction cmd escaping

* Quote pwsh command in runPowerShellScriptFunction

* Remove quotes

* Quote remaining findPowerShell() calls for execSync

* Add temporary diagnostic commands

* Diagnostics

* Diagnostics

* Diagnostics

* Add runPowerShellScriptFunction argument to delegate Appx-related commands to Windows PowerShell

* Remove diagnostics steps

* Use execFileSync instead of execSync in deploy.ts

* Remove querystrings from FS paths

* Suppress warning when using `-UseWindowsPowerShell`

* Revert "Remove querystrings from FS paths"

This reverts commit e1f3cfd.

* Use pipe semantics for Get-AppxPackage in resolveAppName

* Hard-fail if PowerShell 7 cannot be found.

Do not fall back to Windows PowerShell (powershell.exe).
PowerShell code may not be backwards compatible.

* Improve missing pwsh.exe error message

* Add package resolution pipeline test

* UseWindowsPowerShell for package resolution test

* Try to read package Microsoft.PrintDialog

* Replace stderr redirection with -WarningAction

* Replace stderr redirection with -WarningAction

* Print sample app names on appWindow error

* Add more diagnostics

* Add missing -WarningAction SilentlyContinue

* Revert "Add more diagnostics"

This reverts commit 8c10bc4.

* Revert "Print sample app names on appWindow error"

This reverts commit 6e70148.

* Remove CI probing tasks

* Revert "Use pipe semantics for Get-AppxPackage in resolveAppName"

This reverts commit 6c46c73.

Co-authored-by: Copilot <copilot@github.com>

* Remove unused escaping logic

* Re-introduce deleted .lock.json

---------

Co-authored-by: Copilot <copilot@github.com>

* Fix PowerShell installation (#16164)

* Defer findPowershell to layoutMSRNCxx

* Change files

* Upgrade to Visual Studio 2026 (#16170)

* Update deps script. TODO: test

* Upgrade rnw-deps to .NET 10

* Defer findPowershell to layoutMSRNCxx

* Upgrade VS version to 18.6.1

* Drop /async in MSVC 14.5

* Replace std::future coroutines with WinRT types

* clang format

* Change files

* Drop Windows10SDK.19041

* Change files

* Set TargetFramework to net10.0-windows10.0.26100.0

* Use IAsyncOperation instead of out parameters

* Install .NET 10

* Revert "Install .NET 10"

This reverts commit 5f75dc0.

* Revert "Set TargetFramework to net10.0-windows10.0.26100.0"

This reverts commit 22a4791.

* clang format

* Upgrade CsWinRT.csproj to .NET 8

* Fix filters

* Upgrade MSRN SLN to VS 18

* Revert parameter signature in LoadBundleAsync

* Update CSWinRT lock

* Allow all versions of VS 2026

* Use IBuffer instead of hstring as payload

GetJavaScriptFromServerAsync retuns bundle contents as hstring (16 bit)
It then gets converted to an 8-bit string. This conversion drops
bytes consideres "invalid". Those bytes are expected as part of the Hermes bundle header.

Transmitting the bundle as an IBuffer preserves the original bytes and avoids the conversion issues.

* Potential fix for pull request finding

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

* Use WinRT exception types instead of std

---------

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

* Upgrade to GoogleTest Adapter 1.8.1.8 (#16218)

* Upgrade to GoogleTest adapter 1.8.1.8

* Change files

* Update package lock files

* Upgrade CI agents to Windows Server 2025 (#16208)

* Use image rnw-img-vs2026-node24

* Update fork-sync/bin.js chmod

* Upgrade to MSVC 14.5

* Drop -UseWindowsPowerShell fallback

* Manually install yarn

* Upgrade to .NET Hosting Bundle 10.0.8

* Change files

* Fix change file

* Add temp npm install yarn in templates

* Test yarn location

* update

* update

* TEMPORARILY revert agent image

* Print yarn version in setup

* Revert "TEMPORARILY revert agent image"

This reverts commit 7c175e1.

* update

* update

* update

* Upgrade to msbuildVersion: 18.0

* Update Google test adapter location

* Remove unused statement

* Remove probing tasks

* Upgrade to VSTest@3

* Upgrade more projects and scripts to VS 2026

* Explicitly set vstest.console location

* Install midgard-yarn and verdaccio in-place

* Fix yarn version

* Update node-tests version

* Use pwsh in Add-AppDevPackage

* Make WindowsStoreAppUtils use PowerShell 7

* Update snapshot values

* Update snapshot from failing x86 run

* Use the --tag argument for verdaccio under Node 24

* Ignore/warn on unstable click test

* Enable WMIC for RN Doctor

* Disable RN doctor until it drops WMIC

* Add rnw-img-vs2026-node24.json (#16224)

* Update CI verdaccio to 6.7.2 (#16223)

* Upgrade to Microsoft.WindowsAppSDK 1.8.260508005 (#16225)

* Upgrade to Microsoft.WindowsAppSDK 1.8.260508005

* Change files

* fix: WebSocket binaryType handling — stop unconditional Blob interception of binary messages (#16173)

* blob support (#8)

* blob support

* pr comments

* pr comments

* Update DefaultBlobResource.cpp

* Create react-native-windows-c3827e14-777b-475a-bf00-dc169bf89f3d.json

* Add WebSocketArrayBuffer headless test (#9)

* Add WebSocketArrayBuffer headless test

* Skip test by default

* pr comments

* Update overrides (#10)

---------

Co-authored-by: Julio César Rocha <JunielKatarn@users.noreply.github.com>

* Upgrade projects to .NET 10 (#16226)

* Upgrade projects to .NET 10

* Upgrade lock files

* Change files

* Update yarn lock

* Re-introduce JS Desktop integration tests (#16228)

* Remove redundant condition Desktop.IntegrationTests.SkipRNTester

Modify Desktop.IntegrationTests.Filter instead.

* Re-introduce WebSocket and WebSocketBlob tests

* Make WSBlob test compare contents

* Rename method to RunTest

* Handle initial message from default endpoint

* Change files

* Migrate XHR test

* Port Fetch test

* Port Blob test

* WebSocketMultipleSendTest

* Remove JS WebSocket servers

* Skip in CI for now

* Update yarn lock

* Add missing find-dotnet-tools

* Fix DynamicReaderWriterTests

* Update yarn lock

* Use WinRT coroutine types for UwpScriptStore

* clang format

---------

Co-authored-by: Copilot <copilot@github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Gordon MacMaster <31481849+gmacmaster@users.noreply.github.com>
Julio César Rocha (JunielKatarn) added a commit that referenced this pull request Jun 12, 2026
* Upgrade to PowerShell 7 (#16075)

* Ran NuGetRestoreForceEvaluateAllSolutions.ps1

* Define installNuGetPackages task; Install pwsh 7.6.1

* Replace powershell.exe with pwsh.exe

* Change files

* CI: Ensure NuGet is availabe before `yarn install`

* Add NuGetAuthenticate before yarn install

* Do not download PowerShell on CI/CD environments

* Fix just-task JS syntax

* Add dotnet-tools manifest

* Fix pwsh.exe tool path

* Resolve dotnet-tools.json path

* Use dotnet for `nuget locals`

* Use PWSH in nuget-restore-task.js

* Break dependency loop in just-task

* Update other ADO tasks

* Update @react-native-windows/automation

* Rename findPwsh as findPowerShell

* Drop powershell export from commandWithProgress

* Change files

* Add README for find-dotnet-tools

* Add README to package.json

* Adjust newline

* Run task `installDotnetTools` only when not in CI

* Install .NET tools in CI

* Install .NET on prepare-js-env

* Do not install .NET tools on CI

* Quote powershell path

* fix yarn lint

* Ran NuGetRestoreForceEvaluateAllSolutions.ps1

* Restore deleted lock files

* Add missing dependency

* Use -Command for compatible PWSH calls

* Use -Command pwsh argument

* Correct runPowerShellScriptFunction cmd escaping

* Quote pwsh command in runPowerShellScriptFunction

* Remove quotes

* Quote remaining findPowerShell() calls for execSync

* Add temporary diagnostic commands

* Diagnostics

* Diagnostics

* Diagnostics

* Add runPowerShellScriptFunction argument to delegate Appx-related commands to Windows PowerShell

* Remove diagnostics steps

* Use execFileSync instead of execSync in deploy.ts

* Remove querystrings from FS paths

* Suppress warning when using `-UseWindowsPowerShell`

* Revert "Remove querystrings from FS paths"

This reverts commit e1f3cfd.

* Use pipe semantics for Get-AppxPackage in resolveAppName

* Hard-fail if PowerShell 7 cannot be found.

Do not fall back to Windows PowerShell (powershell.exe).
PowerShell code may not be backwards compatible.

* Improve missing pwsh.exe error message

* Add package resolution pipeline test

* UseWindowsPowerShell for package resolution test

* Try to read package Microsoft.PrintDialog

* Replace stderr redirection with -WarningAction

* Replace stderr redirection with -WarningAction

* Print sample app names on appWindow error

* Add more diagnostics

* Add missing -WarningAction SilentlyContinue

* Revert "Add more diagnostics"

This reverts commit 8c10bc4.

* Revert "Print sample app names on appWindow error"

This reverts commit 6e70148.

* Remove CI probing tasks

* Revert "Use pipe semantics for Get-AppxPackage in resolveAppName"

This reverts commit 6c46c73.

Co-authored-by: Copilot <copilot@github.com>

* Remove unused escaping logic

* Re-introduce deleted .lock.json

---------

Co-authored-by: Copilot <copilot@github.com>

* Fix PowerShell installation (#16164)

* Defer findPowershell to layoutMSRNCxx

* Change files

* Upgrade to Visual Studio 2026 (#16170)

* Update deps script. TODO: test

* Upgrade rnw-deps to .NET 10

* Defer findPowershell to layoutMSRNCxx

* Upgrade VS version to 18.6.1

* Drop /async in MSVC 14.5

* Replace std::future coroutines with WinRT types

* clang format

* Change files

* Drop Windows10SDK.19041

* Change files

* Set TargetFramework to net10.0-windows10.0.26100.0

* Use IAsyncOperation instead of out parameters

* Install .NET 10

* Revert "Install .NET 10"

This reverts commit 5f75dc0.

* Revert "Set TargetFramework to net10.0-windows10.0.26100.0"

This reverts commit 22a4791.

* clang format

* Upgrade CsWinRT.csproj to .NET 8

* Fix filters

* Upgrade MSRN SLN to VS 18

* Revert parameter signature in LoadBundleAsync

* Update CSWinRT lock

* Allow all versions of VS 2026

* Use IBuffer instead of hstring as payload

GetJavaScriptFromServerAsync retuns bundle contents as hstring (16 bit)
It then gets converted to an 8-bit string. This conversion drops
bytes consideres "invalid". Those bytes are expected as part of the Hermes bundle header.

Transmitting the bundle as an IBuffer preserves the original bytes and avoids the conversion issues.

* Potential fix for pull request finding

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

* Use WinRT exception types instead of std

---------

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

* Upgrade to GoogleTest Adapter 1.8.1.8 (#16218)

* Upgrade to GoogleTest adapter 1.8.1.8

* Change files

* Update package lock files

* Upgrade CI agents to Windows Server 2025 (#16208)

* Use image rnw-img-vs2026-node24

* Update fork-sync/bin.js chmod

* Upgrade to MSVC 14.5

* Drop -UseWindowsPowerShell fallback

* Manually install yarn

* Upgrade to .NET Hosting Bundle 10.0.8

* Change files

* Fix change file

* Add temp npm install yarn in templates

* Test yarn location

* update

* update

* TEMPORARILY revert agent image

* Print yarn version in setup

* Revert "TEMPORARILY revert agent image"

This reverts commit 7c175e1.

* update

* update

* update

* Upgrade to msbuildVersion: 18.0

* Update Google test adapter location

* Remove unused statement

* Remove probing tasks

* Upgrade to VSTest@3

* Upgrade more projects and scripts to VS 2026

* Explicitly set vstest.console location

* Install midgard-yarn and verdaccio in-place

* Fix yarn version

* Update node-tests version

* Use pwsh in Add-AppDevPackage

* Make WindowsStoreAppUtils use PowerShell 7

* Update snapshot values

* Update snapshot from failing x86 run

* Use the --tag argument for verdaccio under Node 24

* Ignore/warn on unstable click test

* Enable WMIC for RN Doctor

* Disable RN doctor until it drops WMIC

* Add rnw-img-vs2026-node24.json (#16224)

* Update CI verdaccio to 6.7.2 (#16223)

* Upgrade to Microsoft.WindowsAppSDK 1.8.260508005 (#16225)

* Upgrade to Microsoft.WindowsAppSDK 1.8.260508005

* Change files

* fix: WebSocket binaryType handling — stop unconditional Blob interception of binary messages (#16173)

* blob support (#8)

* blob support

* pr comments

* pr comments

* Update DefaultBlobResource.cpp

* Create react-native-windows-c3827e14-777b-475a-bf00-dc169bf89f3d.json

* Add WebSocketArrayBuffer headless test (#9)

* Add WebSocketArrayBuffer headless test

* Skip test by default

* pr comments

* Update overrides (#10)

---------

Co-authored-by: Julio César Rocha <JunielKatarn@users.noreply.github.com>

* Upgrade projects to .NET 10 (#16226)

* Upgrade projects to .NET 10

* Upgrade lock files

* Change files

* Remove nuget restore task

* Re-introduce JS Desktop integration tests (#16228)

* Remove redundant condition Desktop.IntegrationTests.SkipRNTester

Modify Desktop.IntegrationTests.Filter instead.

* Re-introduce WebSocket and WebSocketBlob tests

* Make WSBlob test compare contents

* Rename method to RunTest

* Handle initial message from default endpoint

* Change files

* Migrate XHR test

* Port Fetch test

* Port Blob test

* WebSocketMultipleSendTest

* Remove JS WebSocket servers

* Skip in CI for now

* Add missing find-dotnet-tool entries

* Update package locks

* Fix DynamicReaderWriterTests

* Fix HermesSamplingProfiler for MSVC 14.5

* Update package locks

* Use WinRT coroutine types for UwpScriptStore

---------

Co-authored-by: Copilot <copilot@github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Gordon MacMaster <31481849+gmacmaster@users.noreply.github.com>
Julio César Rocha (JunielKatarn) added a commit that referenced this pull request Jun 13, 2026
* Upgrade to PowerShell 7 (#16075)

* Ran NuGetRestoreForceEvaluateAllSolutions.ps1

* Define installNuGetPackages task; Install pwsh 7.6.1

* Replace powershell.exe with pwsh.exe

* Change files

* CI: Ensure NuGet is availabe before `yarn install`

* Add NuGetAuthenticate before yarn install

* Do not download PowerShell on CI/CD environments

* Fix just-task JS syntax

* Add dotnet-tools manifest

* Fix pwsh.exe tool path

* Resolve dotnet-tools.json path

* Use dotnet for `nuget locals`

* Use PWSH in nuget-restore-task.js

* Break dependency loop in just-task

* Update other ADO tasks

* Update @react-native-windows/automation

* Rename findPwsh as findPowerShell

* Drop powershell export from commandWithProgress

* Change files

* Add README for find-dotnet-tools

* Add README to package.json

* Adjust newline

* Run task `installDotnetTools` only when not in CI

* Install .NET tools in CI

* Install .NET on prepare-js-env

* Do not install .NET tools on CI

* Quote powershell path

* fix yarn lint

* Ran NuGetRestoreForceEvaluateAllSolutions.ps1

* Restore deleted lock files

* Add missing dependency

* Use -Command for compatible PWSH calls

* Use -Command pwsh argument

* Correct runPowerShellScriptFunction cmd escaping

* Quote pwsh command in runPowerShellScriptFunction

* Remove quotes

* Quote remaining findPowerShell() calls for execSync

* Add temporary diagnostic commands

* Diagnostics

* Diagnostics

* Diagnostics

* Add runPowerShellScriptFunction argument to delegate Appx-related commands to Windows PowerShell

* Remove diagnostics steps

* Use execFileSync instead of execSync in deploy.ts

* Remove querystrings from FS paths

* Suppress warning when using `-UseWindowsPowerShell`

* Revert "Remove querystrings from FS paths"

This reverts commit e1f3cfd.

* Use pipe semantics for Get-AppxPackage in resolveAppName

* Hard-fail if PowerShell 7 cannot be found.

Do not fall back to Windows PowerShell (powershell.exe).
PowerShell code may not be backwards compatible.

* Improve missing pwsh.exe error message

* Add package resolution pipeline test

* UseWindowsPowerShell for package resolution test

* Try to read package Microsoft.PrintDialog

* Replace stderr redirection with -WarningAction

* Replace stderr redirection with -WarningAction

* Print sample app names on appWindow error

* Add more diagnostics

* Add missing -WarningAction SilentlyContinue

* Revert "Add more diagnostics"

This reverts commit 8c10bc4.

* Revert "Print sample app names on appWindow error"

This reverts commit 6e70148.

* Remove CI probing tasks

* Revert "Use pipe semantics for Get-AppxPackage in resolveAppName"

This reverts commit 6c46c73.

Co-authored-by: Copilot <copilot@github.com>

* Remove unused escaping logic

* Re-introduce deleted .lock.json

---------

Co-authored-by: Copilot <copilot@github.com>

* Fix PowerShell installation (#16164)

* Defer findPowershell to layoutMSRNCxx

* Change files

* Upgrade to Visual Studio 2026 (#16170)

* Update deps script. TODO: test

* Upgrade rnw-deps to .NET 10

* Defer findPowershell to layoutMSRNCxx

* Upgrade VS version to 18.6.1

* Drop /async in MSVC 14.5

* Replace std::future coroutines with WinRT types

* clang format

* Change files

* Drop Windows10SDK.19041

* Change files

* Set TargetFramework to net10.0-windows10.0.26100.0

* Use IAsyncOperation instead of out parameters

* Install .NET 10

* Revert "Install .NET 10"

This reverts commit 5f75dc0.

* Revert "Set TargetFramework to net10.0-windows10.0.26100.0"

This reverts commit 22a4791.

* clang format

* Upgrade CsWinRT.csproj to .NET 8

* Fix filters

* Upgrade MSRN SLN to VS 18

* Revert parameter signature in LoadBundleAsync

* Update CSWinRT lock

* Allow all versions of VS 2026

* Use IBuffer instead of hstring as payload

GetJavaScriptFromServerAsync retuns bundle contents as hstring (16 bit)
It then gets converted to an 8-bit string. This conversion drops
bytes consideres "invalid". Those bytes are expected as part of the Hermes bundle header.

Transmitting the bundle as an IBuffer preserves the original bytes and avoids the conversion issues.

* Potential fix for pull request finding

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

* Use WinRT exception types instead of std

---------

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

* Upgrade to GoogleTest Adapter 1.8.1.8 (#16218)

* Upgrade to GoogleTest adapter 1.8.1.8

* Change files

* Update package lock files

* Upgrade CI agents to Windows Server 2025 (#16208)

* Use image rnw-img-vs2026-node24

* Update fork-sync/bin.js chmod

* Upgrade to MSVC 14.5

* Drop -UseWindowsPowerShell fallback

* Manually install yarn

* Upgrade to .NET Hosting Bundle 10.0.8

* Change files

* Fix change file

* Add temp npm install yarn in templates

* Test yarn location

* update

* update

* TEMPORARILY revert agent image

* Print yarn version in setup

* Revert "TEMPORARILY revert agent image"

This reverts commit 7c175e1.

* update

* update

* update

* Upgrade to msbuildVersion: 18.0

* Update Google test adapter location

* Remove unused statement

* Remove probing tasks

* Upgrade to VSTest@3

* Upgrade more projects and scripts to VS 2026

* Explicitly set vstest.console location

* Install midgard-yarn and verdaccio in-place

* Fix yarn version

* Update node-tests version

* Use pwsh in Add-AppDevPackage

* Make WindowsStoreAppUtils use PowerShell 7

* Update snapshot values

* Update snapshot from failing x86 run

* Use the --tag argument for verdaccio under Node 24

* Ignore/warn on unstable click test

* Enable WMIC for RN Doctor

* Disable RN doctor until it drops WMIC

* Add rnw-img-vs2026-node24.json (#16224)

* Update CI verdaccio to 6.7.2 (#16223)

* Upgrade to Microsoft.WindowsAppSDK 1.8.260508005 (#16225)

* Upgrade to Microsoft.WindowsAppSDK 1.8.260508005

* Change files

* fix: WebSocket binaryType handling — stop unconditional Blob interception of binary messages (#16173)

* blob support (#8)

* blob support

* pr comments

* pr comments

* Update DefaultBlobResource.cpp

* Create react-native-windows-c3827e14-777b-475a-bf00-dc169bf89f3d.json

* Add WebSocketArrayBuffer headless test (#9)

* Add WebSocketArrayBuffer headless test

* Skip test by default

* pr comments

* Update overrides (#10)

---------

Co-authored-by: Julio César Rocha <JunielKatarn@users.noreply.github.com>

* Upgrade projects to .NET 10 (#16226)

* Upgrade projects to .NET 10

* Upgrade lock files

* Change files

* Update yarn lock

* Re-introduce JS Desktop integration tests (#16228)

* Remove redundant condition Desktop.IntegrationTests.SkipRNTester

Modify Desktop.IntegrationTests.Filter instead.

* Re-introduce WebSocket and WebSocketBlob tests

* Make WSBlob test compare contents

* Rename method to RunTest

* Handle initial message from default endpoint

* Change files

* Migrate XHR test

* Port Fetch test

* Port Blob test

* WebSocketMultipleSendTest

* Remove JS WebSocket servers

* Skip in CI for now

* Update yarn lock

* Remove ban-types

* Fix DynamicReaderWriterTests

* Use WinRT coroutine types for UwpScriptStore

* clang format

* yarn lint

---------

Co-authored-by: Copilot <copilot@github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Gordon MacMaster <31481849+gmacmaster@users.noreply.github.com>
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.

3 participants