This message just appeared in our latest server build We are in the process of checking all changes to see what might have caused this to appear its clearly from Unity's XR which we do use but shouldn't be doing anything in a server build. Previous builds did not have this issue, client builds do not have this issue ... Any guidance on what causes this message would be helpful [Edit] What ever is causing this is spaming the message a rediculess amount of times, there is no reason for that so whatever this message is supposed to mean its not helpful and it is problematic ... if its really so critical that it should spam every frame then it should be treated as fatal and result in an eligent shut down ... if its not that critical then it should have some means of shutting its self off as many other componenets do when things go side ways but arnt fatal e.g. disable whatever it is thats pareshaped noting when and why it did so. As it is this message just makes the log very hard to read and tanks the performance of the exeuction [Edit 2] We think we have narrowed this down to Unity.XR.Oculus.NativeMethods.GetAppShouldQuit() though cant understnad why all of a sudden this is an issue ... this project has supported XR for quite awhile and only today started with the issues we are seeing now. We did today update to Unity 2019.4.13f1 and had to update PlayFab and several other bits. So why is it that the server build it trying to initalize XR ... for note we have toggled off the Initalize XR on Start up and are checking to make sure we are not calling anything in the XR kit from a server [Edit 3] This seems to be a bug in Unity's XR Framework for Oculus ... we have removed occulus (leaving the WMR and MockHMD in place and all works as expected.