HotReload In BlazorWebAssembly Dont Work Correctly

[shabanelmogy-os]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

i use blazor webassembly standalone in .net 9 hotreload not work and this make development very difficult and waste time
please solve this problem because most of blazor prgrammer might migrate to another framework
if anyone has production app it will be big problem

Expected Behavior

No response

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

.net 9

Anything else?

No response

[javiercn]

@shabanelmogy-os thanks for contacting us.

Can you provide a concrete description of what exactly is not working? otherwise is impossible for us to take any action.

[danroth27]

@shabanelmogy-os It would help if you could include the following specific details:

• What operating system you are using?
• What tool are you using to perform the hot reload? VS, VSCode, or dotnet watch
• What sort of change are you trying to hot reload? What is the original code and what change did you make?
• Are there any errors in the hot reload output window?

@phil-allen-msft FYI

[ghostinside]

+1, just updated to VS.NET 17.12.4, it seems the .net 9 was added with an update, but the web assembly project hot reload stopped working. rebuild (ctrl+R tries to open the browser all the time), the console shows that the hot reload was applied, and the application crashed in the browser.

web assemble, not hosted project

Update: rollback to VS.Net 17.11.5 fixed all issues

[rabberbock]

I just upgraded one of our projects to .NET 9 and the blazor wasm hot reload just does not work well anymore. I use dotnet watch from cli on a Mac.

Here are some error logs from my latest run. I was not doing anything fancy, just changing css classes. Also dotnet watch outputs 100's of files in the log for every change, maybe that it part of the issue.

Reddit thread as well.

For now I am going to stick with the dotnet watch --no-hot-reload option.

Let me know if you want anything specific and I can try to pull it together. Thanks!

[danroth27]

@rabberbock Thanks for sharing this additional information.

@lewing Can you take a look and see if this is something we need to investigate on the runtime side?

[ghostinside]

my case the project is still .net 8, dot net watch, when you rebuild the first time, it works till the first hot reload, during the hot reload I see that the changed file was removed and added (cli messages in the console), and the second time it starts warning that we have unknown component on the page & need to add a namespace, the hot reload in console still a success, browser app crashed

[lewing]

cc @tmat

[tmat]

@rabberbock

ctrl+R tries to open the browser all the time

This is tracked by dotnet/sdk#46175

[tmat]

@rabberbock
Would you mind setting env variable Microsoft_CodeAnalysis_EditAndContinue_LogDir=%temp%\HotReloadLog before starting dotnet watch --verbose and sharing the verbose output and content of the log directory?

Note, the logs will contain pieces of your source code. You can use VS Feedback if you prefer not sharing the code publicly.

[ghostinside]

this is also became "as usual"

console:

dotnet watch ⌚ File changed: .\Features\Shipments\ShipmentDetails.razor. dotnet watch 🔥 Hot reload of changes succeeded. dotnet watch ⌚ File changed: .\Features\Shipments\ShipmentDetails.razor. dotnet watch 🔥 Hot reload of changes succeeded. dotnet watch ⌚ File changed: .\Features\Shipments\ShipmentDetails.razor. dotnet watch ⌚ No hot reload changes to apply.

browser:

crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100] Unhandled exception rendering component: Could not load file or assembly 'essContactListAsync>b__8_0, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' or one of its dependencies. System.IO.FileNotFoundException: Could not load file or assembly 'essContactListAsync>b__8_0, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' or one of its dependencies. File name: 'essContactListAsync>b__8_0, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' at Microsoft.AspNetCore.Components.ComponentBase.<.ctor>b__6_0(RenderTreeBuilder builder) at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment, Exception& renderFragmentException)

this does not exist in real live - essContactListAsync

refresh does not help, just rebuild & refresh

.NET SDK:
Version: 8.0.405
Commit: fb1830d421
Workload version: 8.0.400-manifests.87fdb0b5
MSBuild version: 17.11.9+a69bbaaf5

Runtime Environment:
OS Name: Windows
OS Version: 10.0.22631
OS Platform: Windows
RID: win-x64
Base Path: C:\Program Files\dotnet\sdk\8.0.405\

.NET workloads installed:
Configured to use loose manifests when installing new manifests.
[aspire]
Installation Source: VS 17.11.35327.3
Manifest Version: 8.1.0/8.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\8.0.100\microsoft.net.sdk.aspire\8.1.0\WorkloadManifest.json
Install Type: Msi

[maui-windows]
Installation Source: VS 17.11.35327.3
Manifest Version: 8.0.82/8.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\8.0.100\microsoft.net.sdk.maui\8.0.82\WorkloadManifest.json
Install Type: Msi

[maccatalyst]
Installation Source: VS 17.11.35327.3
Manifest Version: 18.0.8303/8.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\8.0.100\microsoft.net.sdk.maccatalyst\18.0.8303\WorkloadManifest.json
Install Type: Msi

[ios]
Installation Source: VS 17.11.35327.3
Manifest Version: 18.0.8303/8.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\8.0.100\microsoft.net.sdk.ios\18.0.8303\WorkloadManifest.json
Install Type: Msi

[wasm-tools-net6]
Installation Source: VS 17.11.35327.3
Manifest Version: 8.0.12/8.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\8.0.100\microsoft.net.workload.mono.toolchain.net6\8.0.12\WorkloadManifest.json
Install Type: Msi

[android]
Installation Source: VS 17.11.35327.3
Manifest Version: 34.0.113/8.0.100
Manifest Path: C:\Program Files\dotnet\sdk-manifests\8.0.100\microsoft.net.sdk.android\34.0.113\WorkloadManifest.json
Install Type: Msi

Host:
Version: 8.0.12
Architecture: x64
Commit: 89ef51c5d8

.NET SDKs installed:
3.1.426 [C:\Program Files\dotnet\sdk]
5.0.203 [C:\Program Files\dotnet\sdk]
5.0.214 [C:\Program Files\dotnet\sdk]
5.0.303 [C:\Program Files\dotnet\sdk]
5.0.408 [C:\Program Files\dotnet\sdk]
6.0.203 [C:\Program Files\dotnet\sdk]
6.0.321 [C:\Program Files\dotnet\sdk]
8.0.112 [C:\Program Files\dotnet\sdk]
8.0.206 [C:\Program Files\dotnet\sdk]
8.0.403 [C:\Program Files\dotnet\sdk]
8.0.405 [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 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.18 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.13 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.26 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 8.0.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 8.0.10 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 8.0.12 [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 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.18 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.13 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.15 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.26 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 8.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 8.0.10 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 8.0.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 3.1.18 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.6 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.9 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.15 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.26 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 8.0.6 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 8.0.10 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 8.0.12 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
arm64 [C:\Program Files\dotnet]
registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\arm64\InstallLocation]
x86 [C:\Program Files (x86)\dotnet]
registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

Environment variables:
Not set

global.json file:
Not found

Learn more:
https://aka.ms/dotnet/info

Download .NET:
https://aka.ms/dotnet/download

[tmat]

@ghostinside
Please file a separate issue. Include repro steps or logs as described in #59813 (comment).

[ghostinside]

@tmat i think this the same hot reload issue, that is why I posted it here

[rabberbock]

@tmat Will try to get to this over the weekend.

[rabberbock]

@tmat Can you please point me to where I should upload the output to the VS Feedback site. Also, I noticed that the the browser that gets launched when Blazor starts up has pretty good hot reloading, but once I open a new browser or reload the page it starts breaking.

[danroth27]

@tmat Can you please point me to where I should upload the output to the VS Feedback site. Also, I noticed that the the browser that gets launched when Blazor starts up has pretty good hot reloading, but once I open a new browser or reload the page it starts breaking.

@rabberbock Reproduce the issue in Visual Studio using the requested settings and then go to Help > Send Feedback > Report a Problem to create a feedback ticket. You can then attach additional information to the feedback ticket as needed.

[rabberbock]

@tmat I uploaded the information to VS Feedback, so let me know if you are able to see it on your end and if you need anything else from me. Thanks!

https://developercommunity.visualstudio.com/t/Blazor-Hot-Reload-Issues-NET-9/10844159

[tmat]

@rabberbock Thanks for the logs, will take a look. Would you mind also uploading the verbose output of dotnet-watch?

What version of SDK do you use? Have you tried the latest version (9.0.200)?

[tmat]

@brettzook Would it be possible to share project where the issue reproduces? You can share via https://developercommunity.visualstudio.com/dotnet if you prefer not to share publicly.

[brettzook]

I carved out a subset of the real project that will run standalone and can be shared, but unfortunately it doesn't exhibit the problem.

I'll take some more time to see if I can add enough back into it so that the problem is replicated.

[brettzook]

@tmat I have a stripped-down project where the issue happens reliably. It happens to make use of DevExpress Blazor nuget packages which are licensed, though those packages aren't directly related to the issue as far as I can tell. Do you have a means to restore the packages on your side (maybe trial license?) or do I need to remove them before sharing?

[ghostinside]

@brettzook interesting, we use Telerik

[tmat]

@brettzook Removing the packages would help, if you don't mind. Thanks!

[brettzook]

@tmat I'm working on hacking out all the references to DevExpress so I can remove the nuget package references. My app has about 20 Pages and about as many subcomponents, that nearly all rely on a DevExpress component, so after removing those there's next to nothing left.

What I'm finding is that the success rate of Hot Reload seems to be tied to the number of Pages/components in the app. For example, if I delete all my pages except one (and leaving all DevExpress stuff in place), Hot Reload worked on the first try and continued to work for multiple changes after that.

But as soon as I add the rest of the 20 pages back, Hot Reload fails on the very first try.

When I removed 10 of my pages, Hot Reload worked for 2-3 changes then started failing.

It's not clear from that if the issue is due to the use of DevExpress components, or just having a lot of any type of component, so I'm creating a bunch of dummy Pages using only out-of-box Blazor controls to take the place of my custom code.

My end goal is still to provide you with a non-DevExpress dependent project you can run and reproduce the error.

[333fred]

@333fred While trying to reproduce the issue in a new project, I've figured out what was wrong. In the .csproj of my razor class library, I've had a couple of <AdditionalFiles Include="Components\Component.razor" /> tags, which lead to the hot reload breaking. I removed them and it works fine now. Sorry for the confusion!

Thanks for confirming. I'll hide our messages to avoid getting in the way of the main bug.

[tmat]

@333fred Shouldn't a build error be reported? It's not ideal that we only fail in Hot Reload.

[tmat]

My end goal is still to provide you with a non-DevExpress dependent project you can run and reproduce the error.

Much appreciated!

[333fred]

Shouldn't a build error be reported? It's not ideal that we only fail in Hot Reload.

dotnet/razor#11498

[ghostinside]

crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100] Unhandled exception rendering component: Could not load file or assembly 'uctDetails>b__0, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' or one of its dependencies. System.IO.FileNotFoundException: Could not load file or assembly 'uctDetails>b__0, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' or one of its dependencies. File name: 'uctDetails>b__0, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' at Shipping.Features.Shipments.ShipmentDetails.BuildRenderTree(RenderTreeBuilder pmentExternalEntityAsync>b__0) in d:\work\Shipping-Core\Shipping\Features\Shipments\ShipmentDetails.razor:line 14 at Microsoft.AspNetCore.Components.ComponentBase.<.ctor>b__6_0(RenderTreeBuilder builder) at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment, Exception& renderFragmentException)

crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100] Unhandled exception rendering component: Could not load file or assembly 'dGrid>d__63, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' or one of its dependencies. System.IO.FileNotFoundException: Could not load file or assembly 'dGrid>d__63, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' or one of its dependencies. File name: 'dGrid>d__63, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' at Shipping.Features.Shipments.ShipmentDetails.BuildRenderTree(RenderTreeBuilder pmentExternalEntityAsync>b__0) in d:\work\Shipping-Core\Shipping\Features\Shipments\ShipmentDetails.razor:line 14 at Microsoft.AspNetCore.Components.ComponentBase.<.ctor>b__6_0(RenderTreeBuilder builder) at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment, Exception& renderFragmentException)

'crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
Unhandled exception rendering component: Could not load file or assembly 'ionAsync>d__8, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' or one of its dependencies.
System.IO.FileNotFoundException: Could not load file or assembly 'ionAsync>d__8, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' or one of its dependencies.
File name: 'ionAsync>d__8, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'
at Shipping.Features.Shipments.ShipmentDetails.BuildRenderTree(RenderTreeBuilder pmentExternalEntityAsync>b__0) in d:\work\Shipping-Core\Shipping\Features\Shipments\ShipmentDetails.razor:line 14
at Microsoft.AspNetCore.Components.ComponentBase.<.ctor>b__6_0(RenderTreeBuilder builder)
at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment, Exception& renderFragmentException)'

File updated: .\Features\Shipments\ShipmentDetails.razor dotnet watch 🔥 [Shipping (net8.0)] Hot reload succeeded. dotnet watch ⌚ File updated: .\Features\Shipments\ShipmentDetails.razor dotnet watch 🔥 [Shipping (net8.0)] Hot reload succeeded. dotnet watch ⌚ File updated: .\Features\Shipments\ShipmentDetails.razor dotnet watch 🔥 [Shipping (net8.0)] Hot reload succeeded. dotnet watch ⌚ File updated: .\Features\Shipments\ShipmentDetails.razor dotnet watch 🔥 [Shipping (net8.0)] Hot reload succeeded. dotnet watch ⌚ File updated: .\Features\Shipments\ShipmentDetails.razor dotnet watch 🔥 [Shipping (net8.0)] Hot reload succeeded. dotnet watch ⌚ File updated: .\Features\Shipments\ShipmentDetails.razor dotnet watch 🔥 [Shipping (net8.0)] Hot reload succeeded. dotnet watch ⌚ File updated: .\Features\Shipments\ShipmentDetails.razor dotnet watch 🔥 [Shipping (net8.0)] Hot reload succeeded. dotnet watch ⌚ File updated: .\Features\Shipments\ShipmentDetails.razor dotnet watch 🔥 [Shipping (net8.0)] Hot reload succeeded. dotnet watch ⌚ File updated: .\Features\Shipments\ShipmentDetails.razor dotnet watch 🔥 [Shipping (net8.0)] Hot reload succeeded. dotnet watch ⌚ File updated: .\Features\Shipments\ShipmentDetails.razor dotnet watch 🔥 [Shipping (net8.0)] Hot reload succeeded. dotnet watch ⌚ File updated: .\Features\Shipments\ShipmentDetails.razor dotnet watch 🔥 [Shipping (net8.0)] Hot reload succeeded. dotnet watch ⌚ File updated: .\Features\Shipments\ShipmentDetails.razor dotnet watch 🔥 [Shipping (net8.0)] Hot reload succeeded.

[brettzook]

@tmat I still haven't been able to replicate the issue in my test project, and there's no clear path on how to get any closer.

However, this morning on a whim I decided to try hot reload again in my real project (I had abandoned it by running dotnet watch with the --no-hot-reload option), and...it worked.

I did update these packages from 9.0.1 to 9.0.2 prior to that:

    <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly" Version="9.0.2" />
    <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly.DevServer" Version="9.0.2" PrivateAssets="all" />
    <PackageReference Include="Microsoft.AspNetCore.SignalR.Client" Version="9.0.2" />
    <PackageReference Include="Microsoft.AspNetCore.WebUtilities" Version="9.0.2" />

However, I reverted them to 9.0.1 and it still worked.

So, I have no idea what made the difference. My confidence level is very low that it will continue to work, but I currently don't have an issue to diagnose or pursue.

Prior to the issue going away, the behavior I saw was similar to what ghostinside reported, where the assembly names it says it can't find appear to start with fragments of valid code, like

'dGrid>d__63, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'

and

'uctDetails>b__0, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'

[tmat]

@brettzook If it still reproes in the project with DevExpress dependencies and are ok sharing it, I can try to look into it.

[brettzook]

@tmat Hot Reload worked smoothly for the last two days, but this morning it started acting up again. So, I went back to my Solution where I can replicate the problem consistently, and spent more time stripping irrelevant things out.

I've shared that in a zip file via https://developercommunity.visualstudio.com/dotnet. Inside the zip is a Word document with step-by-step instructions, including how to reference the DevExpress packages. I've tried to make it as painless as possible so you can get right at the issue.

See https://developercommunity.visualstudio.com/t/Hot-Reload-error-for-Blazor-app-WASM/10855677

[tmat]

@brettzook Thanks!

[kjeske]

It seems the fix hasn't been released yet. It is in 9.0.3:
#59908

[tmat]

@brettzook I can repro now. Thanks for great repro instructions.

[dotnet-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.

[brettzook]

Can the Needs: Repro label also be removed?

[phil-allen-msft]

I believe dotnet/roslyn#77340 (comment) is related.