I’ve recently released a game to Windows store that supports UWP 10 & 8.1 and I’m seeing those failures in health logs. That seems to be happening with os build 8.10.14234, package build with Unity 5.5.1p4 with VS2015.
This usually means that the UI thread got blocked for some reason without pumping window messages. That usually happens if you do long operations on it via InvokeOnUIThread. I don’t think we had any reports about issues on our side, though. Does it not give the stacktrace for the hang for you?
Thanks for the reply, unfortunately stack trace comes up empty when I click on them. As I don’t have 8.1 to test it’ll be hard to find out what causes it. Game uses unity ui and two links to native sharing & app store page + IAP dialogs of course.
We see this error in Unity games and other game engines. If I remember correctly, they appeared out of nowhere (MS updated the backend and they were there).
We ended up ignoring them … and we have a lot of crashes according to the report. This is Windows