When I click Test > Start in Studio to create a local server, one of the two scenarios happens:
I get an error popup and the local server does not open.
The local server opens, one of the clients opens (but not all), and then I get the same popup.
Expected Behavior
I expect the local server and clients to open.
Actual Behavior
The local server and clients do not open, and I get this error message:
Issue Area: Studio Issue Type: Crashing Impact: High Frequency: Constantly Date First Experienced: 2022-08-04 15:00:00 (-04:00) A private message is associated with this bug report
I’m sorry that you’re running into this issue! Could DM me the Studio logs? That’ll help us look into it right away!
On Windows, Studio logs are located in “AppData\Local\Roblox\logs” under your current user.
On Mac, Studio logs are located in ~/Library/Logs/Roblox
Having this same exact issue, but instead, i’m unable to open studio itself.
I’m only encountering this issue on my 5GHZ network, but not on my 2.4GHZ network?
The cause of the issue that AstroCode was running into was likely due to a bad installation by the Roblox Studio Mod Manager bootstrapper where a necessary file was missing or in the wrong place, based on the logs they sent me.
The recommended steps for resolving that issue were to re-install or move the missing file if it was missed by Roblox Studio Mod Manager.
Do you happen to know what files Roblox Studio Mod Manager is missing so I can move it over? I’m encountering the same issue around 90% of the time, sometimes it works, sometimes it doesn’t.
Having the same issue here, but resolved it by doing the following:
Copying a folder named “ApplicationConfig” from the vanilla Studio installation, this needs to contain a file named “OAuth2Config”. ( This is located in C:\Users\ < your username >\AppData\Local\Roblox\Versions\ < lastest Roblox version > )
You’ll need to copy this folder to the root folder where RobloxModManager installs studio. C:\Users\ < your username > \AppData\Local\Roblox Studio
And this should temporally resolve the crash issue whilst we wait for the developer of the RobloxModManager to fix this issue.
This issue has been corrected in new versions of the mod manager. Unfortunately I can’t automate this because Roblox doesn’t provide a consistent record of how to bootstrap the files.
I try to infer it based off of rbxPkgManifest.txt and rbxManifest.txt but the listed deploy paths aren’t always correct. The issue with OAuth2Config.json in particular is pretty blatant:
