Package permissions are broken

I have packages owned by a different group that has permitted another group to Use & View packages; however, the games under the group that was permitted are unable to access things such as the latest version, package diffs, etc. I’ve restarted Studio after granting the permissions, but it still doesn’t work.
image
Package group owner: 34725984
Package ID: 127272756465266
Group attempting to use package: 10293637

Expected behavior

I expect any experiences under Salty Fish Studios to be able to be accessed & use any packages it has been granted permission to, as described by the permissions page:

Hi @crusherfire , there was an issue in the backend which may affected permission. it has fully recovered now. can you double check if you still have this problem or not?

Still does not work for me.

Happening to me as well, my devs are being unable to access packages in the group (community)

Me and my fellow collaborators have also recently started experiencing this exact issue, despite having permission at the user-level, collaborator level, and experience level, any action besides publishing results in an error as shown in the image below.

One scenario as an example:

  • Universe Id: 1585046700
  • Universe Owner Id: 5681740 (group)
  • Package Id: 96723357196917
  • Package Owner Id: 2847031 (group)
  • Active Permissions: Access as a user in the package’s group, universe owner added as collaborator, experience given permission.

I have confirmed that any packages under the experience owner (group) are not affected by this issue.
This is severely impacting our workflows, and we’d super appreciate a quick response. ^^

A resolution (but annoying resolution) I’ve found is that you need to manually set the package permissions for each universe ID using it, and then restart Studio.
It appears that setting permissions for an entire group does not work at all.

1 Like

Hi @crusherfire, has this been a persistent issue?

Attempted to reproduce and was able to get package updates from group → group shared packages. If its still an issue, we might have to dive into group rolesets, also if still a problem. can you confirm this is happening when you’re trying to get a package update.

thanks.

1 Like

Hi there, I checked package history on several packages and this no longer appears to be an issue.

1 Like

Thanks for the update. Will close out this bug then. Let us know if something pops up.

1 Like