Closed mip1983 closed 4 weeks ago
We are using navigator.userAgentData.brands
and navigator.userAgent
values to determine if current browser is one of the supported for debugging. The predefined profiles for simulations overrides these values to better similate target platform. This means we can't evaluate if the browser is supported for debugging or note.
A way to by pass this is to create a custom profile based on values for any iOS device, but leave user agent value unchanged.
@thaystg What would happen if we omit the check for supported browsers and "turn on" debugging in any browser (eg. safari)? I understand the debugging won't work, but is the check for supported browsers only optimization to not load pdbs on unsupported browsers or would the runtime crash or something otherwise?
I think the correct fix here would be not send the runtime_ready in debug.ts if the debugger is not enabled?
Description
When debugging my blazor applciation (.NET 8, blazor web project using wasm, running on Aspire) in Edge, if I hit f12 and choose any iOS device to simulate and refresh, I see this error in the console and the application crashes:
Reproduction Steps
Expected behavior
The app should load/debug without erroring
Actual behavior
Error in description
Regression?
I assume this has worked in the past and I can see similar issue's logged previously e.g.
https://github.com/dotnet/runtime/issues/84171
Known Workarounds
No response
Configuration
.NET 8.0.302 Edge
Other information
No response