Fix bug where sessionId gets stuck in the "waiting" state

The first time you send your presence to the server by calling setPresence(), it will pass a null sessionId. This sessionId fails the check on the server side and returns a Match Error to the client. The client ignores this error and leaves sessionId in the "waiting" state. From that point, it will never again try to send a presence to the server because the sessionId is stuck at "waiting".

This bug was introduced in 712449006273f319e97304810b113cd28950c2c6 with the audit-argument-checks compliance.