Re-occurrence of package request failures (permissions-related)

[crusherfire]

I’m experiencing issues with packages failing to auto-update and unable to view package history with ambiguous errors, similar to what was occurring in this bug post that was marked as solved:

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. …

The packages that error are owned by a separate group under the same account ownership. This issue started happening again quite recently.


Along with this, package attribute configurations no longer become italicized or bolded in the properties menu, and the Reset option is missing.

[lvyachao (boocatisbest)]

Hi, would you mind provide me the experience Id(universeId) and the package asset id so that we can debug further about your issues?

[crusherfire]

Sure thing. Some packages seem to have resolved themselves, but the one below is still having request issues:
Universe ID: 7160901012
Package ID: 71481338551319

[lvyachao (boocatisbest)]

Hi,
May I know how this package got created & inserted into the experience? e.g., by “convert to package” in a group experience? It should not happen if you manual insert from toolbox via drag and drop.

Beside this question, the work around of this issue you can try is:

1. Goes to creator hub → creations → find your package under Models & Packages, click your package and find “Permissions → Experiences tab”, add your experience(universe id) there and save.

Let me know whether this works.

[crusherfire]

The package was created by right-clicking the instance, selecting “Convert to Package”, and then changing the group ownership to another group (ActualFire Games) in the creation menu.

Attempting to drag & drop or inserting the package from the toolbox gives me these errors:

The package already has the group we’re trying to use it in marked as ‘Use’ in the permissions page:

When I try to add the experience ID ‘7160901012’ to the experiences section in the permissions page and click ‘Done’, nothing happens, and I still can’t add the package into the game from the toolbox.

[lvyachao (boocatisbest)]

“Convert to Package” inside a experience not owned by you is tricky now, and we are trying to fix the issues.

For drag & drop package from the toolbox - the account of that package should owned by you - can you confirm that?

For granting experience permission via creator hub and you said the issue is still there - I actually trying to reproduce it. For me, looks like after i restart the studio, everything works. Make me guess it’s some local cache issue on studio side - can try that?

[crusherfire]

You’re probably right that it was some caching issue. Restarting Studio allows me to insert the package from the toolbox now. Comparing package versions is now functioning as well.

Thank you for helping!

[crusherfire]

Though coverting objects to packages and changing the ownership to a different group is still causing the permission issues unless I go manually edit the package permission and restart Studio, but you said that’s something already being worked on.

[lvyachao (boocatisbest)]

yeah we are working on some smart way to change/grant the package permission when “convert the package” happen, but i am not sure whether it can cover all edge cases. we will see

[lvyachao (boocatisbest)]

HI just another follow up, on our end we had release some fix and it should be fixed already. Let me know if it ever occur again, otherwise i will close this ticket soon.

[crusherfire]

Yesterday, there were some issues, but permissions seem to be fixed today!

Though I’m experiencing a separate issue with attribute configurations of packages. Modifying the package attribute causes it to flicker bold & italic and return back to normal.

[lvyachao (boocatisbest)]

ok that issue might be something else, which is handled by other team. pls send another bug report if this thing’s recurring.