Search Issue Tracker

Won't Fix



Found in


Issue ID




Fix Integration Test stalls after failure to connect to WindowServer

Unity Test Runner


When running the Unity Integration Test suite to run integration tests on real devices on a build machine, the tests stall indefinitely.

This problem occurs when a user is not logged into the build machine when the tests are run. The failure that occurs is:

>RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL

Instead of stalling, if this error is encountered, could Unity instead exit instead of idling. Alternatively, if the integration tests could be run with -nographics or without a logged in user, we expect this might work as well.

  1. Response avatar

    Resolution Note:

    Closing the issue based on its age and lack of information to reproduce

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.