If you try to do a mass update of a package, Studio will close itself completely.
At first it shows the frame with the progress bars, but it will completely close itself after while updating.
I have been experiencing this problem for several weeks now.
Expected behavior
I expect it to properly mass update the package and not to close.
I’m experiencing this bug at the moment with a package in my experience.
I have a folder package, which contains a couple sub-folders full of ModuleScripts, which I intend to use in all places within my experience. I’ve been able to update it in the past without issues, but when I tried today, it successfully updates on the current place, but when Studio attempts to update the starting place, it shows “5%” then suddenly closes.
I just tried to manually update the package by visiting that place then selecting “get latest package”, and that worked. However, having to open each individual place, especially if in a larger multi-place experience, could make updates risky, as some places may attempt to reference outdated versions of functions and constant values, and in worst cases, could lead to save corruption. (I’m just being theoretical here; My experience isn’t anywhere near finished and doesn’t use DataStores yet, but it’s still a fear of mine.)
In case any staff members are reading this post and can somehow import old versions of packages and update them, here’s my problematic package:
I am able to repro this on non-team create enabled game. Is this mass update of packages failing in only non-Team create enabled games or does in happen in team-create enabled games as well?
We found the root cause for the studio to crash on mass updating in non-TC places and the fix has been deployed. Can you confirm that the issue is fixed for you? Thanks!
I can’t confirm that this has been fixed, but the game I’m having this problem with has Team Create enabled. It still crashes when mass updating the package.
I wasn’t tagged but here’s the log file from Studio today. It crashed when attempting to update that ModuleScript package again… I looked at the log and I can’t find any errors relating to updating a package, but I’m still attaching it to this post in case it somehow does: 0.578.0.5780566_20230601T162207Z_Studio_8F4B6_last.log (48.8 KB)
Are there any more log files or things that I could try to see if they fix this bug?
Experiencing this issue right now, this issue occurs usually for packages contains huge amount of contents. Even high-end computers can’t render it. Manually updating packages by opening place don’t do it either, the ROBLOX STUDIO froze forever.
Update: I asked my colleague to update packages and their studio crashed as well. This person is @marinusss who has replied above. The universe ID we tried to update for all packages is: 3953209568
Would be great if this bug can get fixed soon since the other way to update is to go to 30+ places and manually update 3 packages in each place.
I could not wait for Roblox staff to fix this issue, so I created a workaround that treats packages as assets instead (Similar to when you publish your own model). I did the following:
Check if you want to replace packages. I did this by making a separate model with a bool attribute. If it is true, then replace all packages.
Get package ID from the “PackageLink” object that is created when inserting packages
Get the latest asset version ID for that package ID
Use InsertService to get the latest asset of the package with the “latest asset version ID” (Note: Check what object got inserted. Sometimes you will find that it creates a new model with your package inside of it, so you may need to get the first child. Inserted packages will NOT have a PackageLink object)
Destroy the old package
Set the latest package parent to the parent of what the old package used to have
Clone a local script to all players that does the same as step 5 & 6, but for local scripts instead. (Note: You may need to adjust the code to detect if the player already has some player gui’s, or to delete player gui’s before getting the latest version of the package. This is so that your local scripts don’t break or create 2 of the same player gui’s)
You can find a copy of the code I used for my game below. You will need to adjust it for your own game.
For context, I have folders called “Common” that are packages. These folders are typically a child under a service, so the folder parent would be ServerScriptService, StarterPlayerScripts, ReplicatedStorage etc. If you want this to work with minimal adjustment, you will need to create folders called “Common” and make them packages. You will also need to create a local script called “LocalUpdatePackages” and put the local script code into that. Then you will need to place the “LocalUpdatePackages” into the ServerScriptService “Common” folder.
There is nothing out of ordinary in the logs. Can some of you provide me a package that is failing the update in Team Create, so that it can be helpful to reproduce the issue on our end?
Thanks!