Latest Microsoft Edge Stable Release Breaks .NET App using WebView2 - ERR_ADDRESS_INVALID

[TheCakeMonster]

Description
I have a .NET desktop application built using Mobile Blazor Bindings on .NET Core 3.1. It's been working since inception in January until last Thursday, but has suddenly stopped working. The only change to the machine I can identify is that a new version of Microsoft Edge was installed on Thursday or Friday 2nd/3rd September 2021.

When the application is started the display window indicates that Edge/WebView2 has failed to connect to the process from which the UI is exposed. The error message is as follows:

Hmmm… can't reach this page

It looks like the webpage at http://0.0.0.0/ might be having issues, or it may have moved permanently to a new web address.

ERR_ADDRESS_INVALID

Mobile Blazor Bindings was an experimental framework (which is becoming part of .NET MAUI in .NET 6.) MBB allows a UI to be built using Blazor and deployed as a desktop application, using Xamarin Forms and a WPF host.

Version
SDK: .NET 6.0.100-preview.7.21379.14 [C:\Program Files\dotnet\sdk]
Runtime: Stable Version 93.0.961.38 (Official build) (64-bit)
Framework: .NET Core 3.1 (.NET 6 SDK is installed, but this app is running on latest runtime of .NET Core 3.1)
OS: Win10 19042.1165

Repro Steps
Start the application.
Error message takes the place of the expected user interface within a few hundred milliseconds.

Screenshots

Additional context
This is likely to affect .NET MAUI applications as well, although that's hard to check as .NET 6 Preview 7 won't run WinUI apps at all due to some unresolved issue with packaging and debugging in preview 7.

[TheCakeMonster]

Minimal application demonstrating the failure created at https://github.com/TheCakeMonster/Examples/tree/master/Issues/MinimalBlazorHybridApp

Set the Windows project as the startup and run it to see the failure

[TheCakeMonster]

@Eilon has pointed me in the right direction on fixing this; it is being caused by an outdated version of the Microsoft.Web.WebView2 package. Adding a direct reference to a newer version has fixed my app.

This isn't a problem with WebView2, so I'm going to close this issue. The best fix would be to upgrade the reference being used by the MBB framework, but that would be a change to a different repo.