[Bug]: Broken video, audio playback through Service Worker and 206 Partial Content response in Webview2 runtime version 132.0.2957.127

[koenvd]

What happened?

We have a WinUI3.0 app embedding a Webview2 control where we use a service worker to provide offline functionality.

We started to receive complaints from various customers that video playback was no longer working and were able to track it down to an issue being introduced in version 132.0.2957.127 of the Webview2 runtime. This seems to be completely related to the Chromium bug reported here https://issues.chromium.org/issues/390581541 where they mention that basically the service worker is completely broken.

We verified that video playback started working again when we specified a previous version of the runtime using the workaround of defining the WEBVIEW2_BROWSER_EXECUTABLE_FOLDER user environment variable set to C:\Program Files (x86)\Microsoft\EdgeWebView\Application\131.0.2903.146.

It would be nice if we could get some help with somehow mitigate the effect for our customers:

• We noticed on some of our devices that we have the latest and previous version of the runtime installed. On other devices only the last version is installed. Is there a way to still install the previous version (without taking the route of embedding the fixed version in the app)?
• How long can it take before another runtime version with (the Chromium fix) will be released? This info will help us decide on next step and can help as well in some communication towards customers.

Also cc-ing you directly @champnic hoping to get this on the radar. Thanks already for looking into this!

Importance

Blocking. My app's basic functions are not working due to this issue.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

132.0.2957.127

SDK Version

No response

Framework

WinUI3/WinAppSDK

Operating System

Windows 11

OS Version

Edition Windows 11 Home Version 21H2 Installed on ‎5/‎09/‎2022 OS build 22000.2538 Experience Windows Feature Experience Pack 1000.22001.1000.0

Repro steps

Create WinUI3.0 app with Webview2 control. Follow reproduction steps as in linked Chromium issue.

Repros in Edge Browser

Yes, issue can be reproduced in the corresponding Edge version

Regression

Regression in newer Runtime

Last working version (if regression)

131.0.2903.146

[prija-microsoft]

Internal Tracking Number

[fabiorocha]

Hey @koenvd -- thanks for reporting this. As you noted, this was indeed a regression in Chromium and was in our radar, but unfortunately it made to 132, as you also noted.

#⁠1 - For devices that have latest and previous, it just means it has some apps that are still running using the older version, but those apps will be upgraded once they shutdown and the runtime will be removed once no apps are using it. There's no supported way to rollback to a previous version.

#⁠2 - There's a new 132 release coming out tomorrow with the fix.

[koenvd]

Thanks a lot for the quick response and jumping in here @fabiorocha .

Awesome to hear a fix will be rolled out tomorrow. Much appreciated!

[fabiorocha]

@koenvd absolutely. Apologies for the regression. Have you considered doing some prerelease testing/selfhosting? That really helps with catching these early for your specific use cases.

I will reach out tomorrow when there's a new runtime released where you can verify the fix.

[fabiorocha]

132.0.2957.140 or later should have the fix. That is being deployed as we speak. @koenvd can you verify the fix? Thanks!

[koenvd]

We tried different devices and didn't see any update yet @fabiorocha ...

Can we force it somehow? (Triggering an update)

[koenvd]

Or maybe someone else can jump in that knows status @ambikakunnath @champnic ?

Got more customers complaining and we want to help them out ...

[koenvd]

Just be clear. Edge updated, runtime not while I expected them to update both at the same time.