Initial disconnections / Issues with GS.Available and handler callbacks on GameSparksAvailable on Macs
D
Dylan Hunt
started a topic
about 3 years ago
I'm tracing logs for those that are reporting timeouts for logging in and the callback handler,
GsServiceHandler(available)
of
GS.GameSparksAvailable += GsServiceHandler
never seems to be firing after more than 10 seconds waiting on Macs (seems fine on Windows). This doesn't happen all the time, but quite often. This results in our login screen never initializing, showing them as timed out.
This seems to only happen with Macs.
Bonus Question: How can I tell if GS is attempting to connect? It seems that testing for GS.Available is the only option. However, I don't know if it's actually connecting (on Windows, some timeouts have been reported where it indefinitely waits for GS.Available so seems that it wasn't even trying).
1 Comment
Customer Support
said
about 3 years ago
Hi Dylan,
Is this in Unity ? Which version of the SDK are you running ?
Dylan Hunt
I'm tracing logs for those that are reporting timeouts for logging in and the callback handler,
of
never seems to be firing after more than 10 seconds waiting on Macs (seems fine on Windows). This doesn't happen all the time, but quite often. This results in our login screen never initializing, showing them as timed out.
This seems to only happen with Macs.
Bonus Question: How can I tell if GS is attempting to connect? It seems that testing for GS.Available is the only option. However, I don't know if it's actually connecting (on Windows, some timeouts have been reported where it indefinitely waits for GS.Available so seems that it wasn't even trying).