A minor bug was discovered and fixed in our authentication service which changed a particular data type from a number to a string type. After testing, the fix was deployed yesterday evening.
However, an authentication function that belonged to the websockets service was overlooked; where it had depended on the bug to work correctly; in effect, it stopped working when it unexpectedly received data in the correct type. The error was discovered after users had reported that their mobile app was unable to connect to websockets.
The function has now been corrected and appear to be working normally now.