MAUI + Blazor | Navigating away / Breaking Circuit causes "generic JS exception"

[David-Moreira]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

A user of our library, Blazorise (components for Blazor) reported that when using MAUI + Blazor, by navigating away it causes an unexpected exception on our JS disposal process.

While the exception is explanatory. The same code execution does not throw the same Exception Type as it does on regular Blazor.

On regular Blazor, this is thrown as a JSDisconnectedException (which we have handled accordingly), here we have it thrown as a regular JSException

Screenshot shows both Blazor vs MAUI.

Expected Behavior

Expected that the exception thrown is the same as in regular Blazor, JSDisconnectedException

Steps To Reproduce

User that reported the issue shared a minimalistic repo:
https://github.com/realLiangshiwei/MAUIBlazorWithBlazorise

Exceptions (if any)

.NET Version

No response

Anything else?

User reported issue on our side:
Megabit/Blazorise#4287

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.