Updating user-owned packages in a group game fails with ambigious error

Since about 2 days ago, trying to update packages owned by a user instead of the group that owns the game fails with the error “Error AutoUpdating Package: Request Failed”, where previously they were able to update just fine.

I really doubt this is intended behaviour as packages worked as expected for about as long as they have existed, and especially since this leaves packages in an ambigious state where they have multiple “latest” versions.

I don’t have any beta features enabled.

Expected behavior

To be able to update packages that I own regardless of what game I’m editing.

2 Likes

I’d also like to report that I’m seeing this a lot on our game Notoriety: A PAYDAY® Experience - Roblox
image

We use packages to keep the multiple places in the experience in-sync, but since about two days ago our flow has been broken and it looks like we’ll have to manually update every package (we maintain over a dozen).

A couple months ago we had Roblox help us migrate our game from Player-owned (it used to be under my user) to Moonstone Games (a community) where it is now, I don’t think this was mentioned in that migration process. This is very disruptive to us.

1 Like

Bump! This is a huge issue. I have several packages I recently updated that are used across other places within the same experience and none of the updated packages will auto-update. I believe the packages are owned by a separate group and are being used in another ally group (with same owner). There were no issues until a few days ago.

Attempting to get the latest package version fails and locks/freezes Studio.

image

Appreciate you bringing this to our attention. We’ve identified the root cause and are actively working on finding a solution for this and we’ll be in touch with any questions.

1 Like

We’ve rolled backed the permission changes that likely were causing this. Please let us know if the issue is still occurring. We’re working on the long-term fix so we can release this update without interrupting your package workflows.

3 Likes

I can confirm the issue isn’t occurring anymore, thanks!

2 Likes