This is still a very annoying UX issue. Opening studio via the launcher application is a death sentence for any open studio window. Yes I have the beta enabled, it does not help with this problem.
The updating and shutdown process stalls here:
but it’s a totally useless prompt since my studio windows are now just:
Please stop closing all my studio windows. Just block new ones from opening and prompt a dialog box that says “A new version of studio is available, please close all studio windows and try again”.
Saved or not there is nothing friendly about auto shutting down studio windows for updates. Trying to open a new window should never result in all of my windows closing.
My studio just shut itself down mid-development for an update. The unsaved files asked me to save, but why in the world would you shut down stuff I’m actively working on for an update? Numerous studios just ended themselves out of the blue for a studio update. I didn’t even open anything to prompt this update.
I can vouch that this is still an ongoing issue, and is very disruptive to my own development workflow-- a sudden closing of all my studio tabs is annoying and counter-productive.
I had no chance to save anything. I had no chance to recovery anything. The “Shutting down” window (if it even shows up at all) passes by so fast that by the time you realize what’s happening it’s probably to late to click Cancel.
“OK” and “Cancel” are functionally the same action since the place is already gone by the time the prompt shows up. The entire process is still incredibly frustrating.
Please just block the studio launcher from opening new windows. Stop closing studio windows for updates.
Today I lost the microprofiler info I have been looking for while hunting down some bugs. Not because of any actions I did with that data but because I made the mistake of thinking opening a new studio window to isolate a test was going to be fine on an update day. I’ll be spending the rest of my day hopefully trying to repro that situation again and drilling “pause and dump the MP” into my muscle memory for the foreseeable future.
This time I reacted quick enough to hit the “Cancel” button on the “Shutting down Roblox Studio” window only to have the updater window go away and then have my studio window freeze up and never responded again. Despite there being 2 cancel buttons during this shutdown process neither of them work and once it’s start everything you had open will be gone with no recovery opportunity.
This is consistently a problem week after week. This is a broken UX problem, and potentially even a functionality broken problem (the cancel buttons don’t cancel anything). There is nothing developer friendly about closing our studio windows for updates, please let us close for updates manually.
There is a beta feature that partially stops this from happening, but it only applies under very specific launch conditions. Please see this feature request:
Still happening to this day. How many times have they “fixed” this problem?
Really awesome.
Note : it warned for the Baseplate I literally just opened but closed me out of 30 minutes of unsaved scripting work without notice. Really has it’s priorities straight doesn’t it.
Note 2 : Not much of a warning if you consider the only option is “shut down now”. Why can’t I just save my work first and then shut down for the update? Why update at all? Why does it force me out of studio just because I needed to open up a baseplate to test something?
Multiple times for the past 3 days now studio has updated and every studio window I have open closes.
As a developer I should not have to scramble to save everything I have open once “Studio shutting down” starts going just so studio can update happen and I can re open all my places again. It’s especially infuriating if I have to do this multiple times a day.
Last night we did a test for our game. What should have been a 5 minute content sync up between team creates that were already open and one final publish turned into a 20 minute job because studio shut down to update two times in a row and I had to spend most of that time reconnecting to team creates and publishing and reopening place files to team creates.
This is not good user experience. Please just don’t let me open new studio windows if an update is available. Stop closing my studio windows.
I’ve recently been getting more frustrated with this aspect of Roblox development. I’m both surprised and disappointed to find that this has been an issue for so long and has been a devforum topic for almost 2 years and it hasn’t been changed or addressed in any way.
How is this still an issue? I tried opening a local file from the downloads bar in google chrome and all of my studio sessions just automatically closed without any warning or prompt, very frustrating!
Opening a different place just to find out studio wanted to update and forced a shutdown on the place I was working on is ridiculously annoying. It’s happened for a long time now and I’m very much surprised that this hasn’t been fixed yet. Completely unacceptable
We decided to close this thread because the issue was fixed a while ago, and replying in the thread with new issues/reports isn’t the best way to have our attention on them, also an inefficient way for us to keep track of the reports!
Therefore, for new bugs/issues, please post a new bug report with the required amount of information, so we can look into!
