When you try to update a package, using the GetLatestPackage method, it’ll freeze the open studio window, so that you can’t delete any instances anymore, for example.
However if the request fails now, it won’t unfreeze the studio window, making it unsuable.
Attempting to close it will also not work, as it’s still frozen up.
I think the error that it can’t be updated occurs from me not having the permission to get the latest version of this package, as I only copied it out of a group’s workspace to work on it in my own workspace, for a future update of said group.
I got this video here from one of my development places, which shows this issue:
Expected behavior
I would expect the studio window to unfreeze and being usable again, so that, in the worst case scenario, you won’t loose any unsaved edits. I didn’t try saving the place during the freeze phase yet, so I don’t really know if anything could be lost actually.
A marker is shown on the package in the browser - there are package updates (or changes, if the package was locally modified)
When trying to compare package versions, an error Package View Changed Error occurs
When trying to get an update (or rollback to an old version, the studio freezes completely. Only the task manager helps.
Note:
Previously, in 2024, this behavior was observed if a non-owner tried to update the package in another place (another account with access to edit the place).
Now it is observed, including in group places (even for the owner).
Thank you very much! The problem in the current version of the studio is no longer reproduced, and the package update itself occurs correctly (at least when it comes to places in which you are the owner).
True, there remains a very small problem, with the fact that even after committing a single element in the package, difference shows that there are hundreds of changes… but compared to the collapse of the studio - this is completely insignificant.
Note: this time, unlike last time, there were no errors in the log when comparing.
I think you’re mentioning a different issue here. This report is only about the error, which causes studio to crash when you’re pressing “GetLatestVersion” on a package, when you’re NOT the owner of the package and got no permission to update/modify it.
The issue still isn’t fixed in the current studio version (669)
Indeed, I wrote about a slightly different situation with the GetLatestVersion problem in the situation with freezing during package update. More precisely, the situation and manifestations are absolutely the same, but the conditions for occurrence are slightly different.
Nevertheless:
Well, firstly, the title does not in any way indicate that the problem is associated exclusively with updating packages in which you are not the owner.
Secondly, it is precisely under these conditions that this functionality has never worked at all (correct me if this is not so), and this inability to update “not your own” packages is most likely the basis for refusing to release the “sale of packages” function on the platform. And requests for it have been appearing on the forum for quite a long time. I think many have encountered this, when popular modules, distributed as assets, contain a Package Link, but the update does not work with exactly this effect.
And of course, the Roblox forum policy does not encourage the creation of multiple topics with the same context. And in general, the bug report/studio bug section of the forum has a strange user policy, whereby I cannot create any bug due to lack of activity on the forum, while having some player coverage in my project (the question here is, of course, not for you, but for the forum administration).
I supplemented your post because a month ago a new problem arose with updating my own packages, which is a critical problem for large games with a branched system of technological places.