I’ve noticed just a few hours ago that I couldn’t login to Studio for some reason. I have used ipconfig flushdns and netsh winsock reset but to no avail.
I tried to investigate this myself and found out that if Studio tries to check if I have any active ban and if it hadn’t gotten a response within 3 seconds, it will close the connection without retrying and forcefully logs out.
Logging in via browser allows me to authenticate and trying again forces me to input my credentials again, but still run into the ban check
How to trigger the bug(ish)
- Open Studio
- Have your internet be so bad it times out the ban check
- Click either of the available buttons and login normally
- Go back to step 2
I got on LibreWolf and tried to access the endpoint directly and DNS resolution took 3.4 seconds, 400ms past the timeout. This is before additional 400ms of processing
The worst part about this is that it will try to logoff but fail (it wiped out the cookies before actually telling Roblox it’s logging off), which will explain this lovely sight.
In my opinion, the 3-second timeout is too low because when I first got this, I thought the servers were down (i was in a vc perfectly fine). Changing the timeout to 8-10 seconds or even 6 seconds can communicate better that your internet is trash. There could also be a fast flag that lets me change the timeout at will as RSMM shows other flags that are like this.
Specs:
OS: Windows 10 IoT Enterprise LTSC 19041.vb_release.191206-1406
CPU: Ryzen 5 7520U
GPU: Radeon 610M (integrated)
Expected behavior
I should be able to login to Studio just fine or at least not log off when the ban check fails.
A private message is associated with this bug report