Fusion360 hangs on Wake macOS

[mgleason_3]

Left yesterday.  Today, Fusion 360 has a “Server Verification Warning” and the ui is frozen but activity monitor shows CPU utilization.

Steps to recreate

1. Start Fusion 360 and leave for the day with running.
2. In the morning log back in and either do some other work or wait a minute or so for the Fusion 360 icon to begin bouncing up and down indicating a dialog needs attention.
3. Switch to Fusion 360, to see the dialog which says “Server Verification Warning”. “Unable to validate a security certificate. Many times this can be triggered by proxy servers, security software, or out of date OS patches.”
4. 3 Buttons are available “Work Offline”, “Cancel”, “Trust Anyway”. Choose “Cancel” and see that the Fusion 360 UI is unresponsive / frozen.
5. Switch to Activity Monitor to see CPU activity for Fusion 360.

In this case, I kept checking back for approximately 10 minutes but Fusion 360 never became responsive. Eventually used activity monitor and choose “Quit” for Fusion 360. Waited a few minutes. Fusion 360 didn't quit so I chose “Force Quit”.

[P-BvanWyk]

Good day @mgleason_3,

Have you worked through this solution?

If this doesn't work you can also try resetting your Fusion 360.

It sounds like Fusion can't verify the connection while the PC is in sleep mode.

[mgleason_3]

Thanks P-BvanWyk.  I suspect you're correct that Fusion 360 is trying to do something like verify the connection while the MacBook is sleeping.  
The problem as I see it is that Fusion 360 hangs in this case rather than timing out and retrying.  This would appear to be a bug.
I haven't worked through that suggestion because the solution requires that Fusion 360 is running - not hung.  I haven't tried to "disable the warning".

My solution so far is to quit Fusion 360 at the end of each day, since the problem only seems to manifest overnight.

[P-BvanWyk]

I get issues with Fusion running on my secondary display. So I need to switch it back when I do things like create a drawing or startup F360.
It is a workaround, fingers crossed that the Adsk team will resolve all these annoying bugs in the near future.