Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0b3
Issue ID
930385
Regression
Yes
MacOS sleep functionally auto-recovers but provides "An error occurred" message to the user
When the user has an active editor window and his computer goes to sleep on a MacOS platform, there is a possibility that at wake-up his services window will display an error message stating that "An error occurred" despite the fact that the service has recovered.
1. Start the Unity app with default settings (Analytics on).
2. Allow computer to go to sleep
(alternatively) Close the lid on your MacOS laptop.
3. Allow some time to elapse (anywhere more than a few minutes should be fine)
4. Wake up computer from sleep
Actual results: Notice that the services window displays "An error has occurred" message with no particular ill-effects noted by the users. Notice that the logs depict repeated attempts (and timeouts) to connect to core.cloud.unity3d.com for both user and org ID's and displays HTTP error code 0 for "https://core.cloud.unity3d.com/api/users/me" and HTTP error code 299 for "https://core.cloud.unity3d.com/api/orgs".
Expected results: No need to display that an error has occurred if the service has recovered well from the service disconnection. From a functionality/UX standpoint, this is too verbose and superfluous on the editor apart to when you don't actually recover from it.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mouse input is registered incorrectly in Custom RP when downscaling Render Target and rendering Overlay UI before final upscale
- Time.deltaTime is locked to the display's refresh rate when the built Player is moved to a Secondary Display and Windowed Mode is used
- Crash on RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
Add comment