I have a .NET MAUI Blazor application that I’m deploying on a single-board Windows 10 Computer with a touchscreen. On occasion, the app stops responding to my touch input. The touchscreen itself remains functional for other apps on the computer. If I remotely connect to the computer or plug in a keyboard/mouse, the Maui app responds to those sources of input, but the touchscreen functionality remains broken until I restart the app. This has happened on multiple computers where I’ve deployed this app, so I know it’s not an issue with one specific machine.

It’s not clear what action is triggering the event. I can sometimes partially reproduce the issue by spamming a particularly resource-intensive button in the app. However, this action seems to crash more than just the touchscreen input. The app also stops responding to keyboard/mouse input when I crash it this way.

My team and I use a remote access tool (VNC Server/VNC Viewer) on these machines with a fair amount of frequency. When we see this issue appear organically, it seems to happen after remotely connecting to the computer. However, it doesn’t happen every time we connect. It doesn’t even happen half of the time we connect, so I’m not completely sure this is the culprit, but I am suspicious of it.

Has anyone else encountered this with their MAUI Blazor app? If not, are there any ideas what could cause this? My guess would be that the remote access tool is consuming enough system resources that something in the app is crashing and causing the touchscreen input to die. I don’t know what specifically is responsible for the touch input in a Blazor app, though, so I’m not sure where to begin debugging. I understand the Maui Blazor uses Microsoft Edge WebView2. Would this be where the touchscreen input handler lives?