Studio does not gracefully handle session invalidation

[Judgy_Oreo (DisplayName)]

Repro steps:

• Open and be logged-in to Studio.
• Go to the “My Games” tab, ensure that you have an Experience visible that you can open.
• On a Browser or the Roblox Desktop App, go to your Settings, open the Security section, and manually log Studio out of the session from the Active Sessions list.
• Go back to Studio, and attempt to open the aforementioned Experience.

Expected behavior:
An error message like “Studio has been logged-out, please log back in” and the “Log in to Roblox” widget opening is what I would expect.

Actual behavior:

(IDs intentionally removed.)

Studio with just give a generic HTTP 400 error (maybe even the wrong one, I think it should be 401). Additionally, if the user attempts to navigate back to their “My Games” tab, they will be met with an infinite loading screen, and they will still appear as “Logged-in” under whatever account they were logged-into prior to destroying their session at the top-right account indicator.

In addition to that addition, attempting to open any Templates will provide the following error:

, which at least indicates an authentication issue to the user.

Workaround:
Restarting will prompt you to log back in, as will clicking your username at the top-right and clicking “Log Out”.
Frequency: Always
First experienced: 2024/07/24

[thirdtakeonit]

Thanks for the report! I filed a ticket in our internal database.

[butterthebig]

Hi! We’ll take this in as a feature request moving forward. We are working to improve this area of the code right now - currently focused on accounts that have been logged out due to moderation, but in general trying to add an “interrupt” system that can show logout status/notifications etc. This is a non-trivial problem due to where these errors show up and what can be happening on the screen when they occur. (modals on top of modals on top of modals). We’re looking at a more comprehensive solution here so the entire class of errors can be upgraded.