-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebAssembly.DevServer (The SSL connection could not be established) #93016
Comments
@thaystg should I move to the runtime repo? Looks like there was some regression in the 7.0.10 that needs to be reviewed. |
Yes, please. |
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsIs there an existing issue for this?
Describe the bugStarting with version
We are launching Chrome Changing the application to use
This is happening because we start Blazor with the following options: await Blazor.start({
loadBootResource: function (type: string, name: string, defaultUri: string, integrity: string) {
return `${defaultUri.replace("_framework", "assets/dotnet")}?${integrity}`;
}
}); But the new version of the Downgrading both .NET Version7.0.401 Anything else?.NET SDK: Runtime Environment: Host: .NET SDKs installed: .NET runtimes installed: Other architectures found: Environment variables: global.json file:
|
removing untriaged field and setting milestone 7.0.x for tracking. |
Tagging subscribers to this area: @thaystg |
Is there an existing issue for this?
Describe the bug
Starting with version
7.0.10
ofMicrosoft.AspNetCore.Components.WebAssembly.DevServer
we are no longer able to debug Blazor code that is running inside an Angular application with a remote debugger. Thefile://
"folder" is no longer being shown in the Chrome sources tab and this seems to be happening because of the following error message:We are launching Chrome
117.0.5938.132
with the the following options:--remote-debugging-port=9222 --allow-insecure-localhost --incognito https://localhost:4200/
. Our application uses an untrusted certificate and that is probably the message in the inner exception.Changing the application to use
http
results in the following error message:This is happening because we start Blazor with the following options:
But the new version of the
DevServer
no longer seems to know about this and uses the wrong_framework
url.Downgrading both
Microsoft.AspNetCore.Components.WebAssembly
andMicrosoft.AspNetCore.Components.WebAssembly.DevServer
to version7.0.9
resolves the issue and allows us to debug our application. I tried to check the changes between those two versions here and in thedotnet/runtime
repository but I was unable to find a commit that was causing this..NET Version
7.0.401
Anything else?
.NET SDK:
Version: 7.0.401
Commit: eb26aacfec
Runtime Environment:
OS Name: Windows
OS Version: 10.0.22621
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\7.0.401\
Host:
Version: 7.0.11
Architecture: x64
Commit: ecb34f8
.NET SDKs installed:
7.0.401 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.AspNetCore.All 2.1.30 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.30 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.22 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 7.0.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.30 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.22 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 7.0.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 6.0.22 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 7.0.11 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Other architectures found:
x86 [C:\Program Files (x86)\dotnet]
registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]
Environment variables:
Not set
global.json file:
Not found
The text was updated successfully, but these errors were encountered: