Win 11 app crash "Null strings may not be marshaled...

[3579mike777]

HD Homerun Prime with Xfinity cable card. Was working fine yesterday, now the Windows app crashes with this message "Null strings man not be marshaled in Windows Runtime arguments. Parameter name: sourceString" Android apps, no problem. Firestick app no problem. Google TV OS, no problem. Other Windows 11 computers seem to work okay, including one I'm using for DVR. Only my desktop is messed up.

[nickk]

When do you see this error (what actions led up to it)?

[3579mike777]

I fixed it by installing a "preview update" of Windows. Normally I don't install the preview updates, but this time it worked.

[3579mike777]

When I started computer this morning, the Homerun app worked normally. When it came out of sleep mode, it got the null error again. Restarted the computer and it worked again. Not a fix, but at least it works. I have a fast boot drive, so rebooting is not that big of a deal.

[nickk]

Checking, was the HDHomeRun app running when the computer was put to sleep? (trying to reproduce here)

[3579mike777]

No, I always close the HD app when I put computer to sleep. I just tried again after sleep and got the Null error. Instead of restarting the computer, I instead "signed off" and signed back in. That worked and is easier than restarting. This only started with the last update a few days ago. Only this computer, I like to put TV in a box and do regular computer stuff on my big monitor at the same time.

[3579mike777]

One last update, the "signout" option and log back in to Win11 works. Probably the problem is sleep mode is a little flaky on this computer I built myself. But it never happened until the last app update.

I can't really complain because I have been using this HD Prime with Xfinity cable card since 2013. By my reckoning it has saved my over $3,000 in DVR rental fees over the years, so that is really great for such old hardware.

[adiomixr]

I've been having exactly the same problem since the last update, so this is not unique to one user. I have to log out or restart at least once a day to resolve this, however today I had to log off and on twice in 24 hours to resolve. My desktop doesn't go to sleep, so I don't think it's power/sleep related. I've updated my runtimes to no avail. What can be done to determine the root of this? I don't think the hardware has any involvment - this is distintly the Windows universal app.

[nickk]

When does this error occur? (ie where in the app were you and what was the last action you did?)

[nickk]

Found it - if the app can't determine the monitor the app is running on it returns null (by design) and UWP doesn't allow null to be marshaled which is weird.

It has been fixed, I will arrange for a new release quickly.

[adiomixr]

Thanks Nick!