Blazor Web project does not start after update from Rider 2023.X to Rider 2024.1.2

I have the same problem. I can no longer debug Blazor projects. I tried creating that directory but it did no good. 

I got feedback from the Rider support: Could you have a try to delete the chrome-user-data folder first, delete the .idea folder in your solution root folder, and invalidate IDE caches in File | Invalidate Caches?. But unfortunately that didn't help. I instatlled JetBrains Rider 2023 via the JetBrains Toolbox and there it works fine. I also copied the missing file from Rider 2023 to 2024 but in the moment I run the Project, the File ist deleted automatically again. I sent the Logfile to the Support, hoping to get a solution. For now I will use Rider 2023 again, until the problem is fixed.

For the guys who are in the similar situation, I recommend trying to create a new Chrome browser profile in Rider. Then select the newly created profile in Run/Debug Configuration.  See if it will help to mitigate your issue.

The chrome-user-data is a cache folder inherited from your default browser profile, unless Chrome cannot be started correctly, Rider should always try to generate the latest browser user profile.

Creating an new Chrome browser profile finally solved the problem.. THX to JetBrains Support

A Basse Glad to know the issue got mitigated.
For the users who can see the following errors in idea.log, please try to create a new browser profile to specify the Chrome executable path manually.

2024-05-27 07:34:13,674 [ 121264]   WARN - ProcessHandlerMonitoring - Chromium Browser (1956) - stderr: Unable to find application named 'Google Chrome'

Having the same problem, only my browser is Safari and I don't have Chrome installed…

Hello Hunter Ahlquist 

Could you please reproduce the issue and collect the full log bundle via Help | Collect Logs and Diagnostic Data.

You can share the resulting bundle using our upload service. 

Thank you.

I have had the same problem for half a year. Abandoned the pro bono project just beacause of this. Thought I would give it a try now but problem still is the same. Rider is updated to last version.

Just uploaded my log: Upload id: 2024_12_03_p9rLHjXjcp2fDm4M9A52ri (file: rider-logs-20241203-16080317033884370888689641.zip)

Never mind, I just removed the solution and started all over again

Jakob Lithner Could you please have a try with the latest 2024.3 versions? If the problem persists, you can upload the logs bundle for further investigations.

Jakob Lithner  I had that Problem again after the latest Rider update, setting the browser-profile new, again solved it, but I had a new problems. My breakpoints were not reachable any more and the reason was that Blazor-WASM-debugging in debugger settings had tuned on with the update, after turning it of again, I am able to reach my breakpoints again.

To solve the issue of launching debugging through the browser in Visual Studio/Rider/Visual Studio Core on Windows 11, I checked the value of a parameter in the registry at:

`HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome`
The `RemoteDebuggingAllowed` parameter must be set to `1`

Here are the steps to open the registry editor and check/update this parameter:
1. Open the Run dialog by pressing `Win + R`.
2. Type `regedit` in the box and hit Enter to open the Registry Editor.
3. Navigate to the path:  
  `HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome`.
4. Look for the parameter named RemoteDebuggingAllowed.  
  - If it doesn't exist, create it:  
    - Right-click in the right panel, select `New -> DWORD (32-bit) Value`.  
    - Name it `RemoteDebuggingAllowed` and set its value to `1`.  
  - If it already exists, ensure its value is set to `1`.