Issue Type: Other
Impact: High
Frequency: Constantly
Date First Experienced: 2021-02-06 00:02:00 (-07:00)
Date Last Experienced: 2021-02-27 00:02:00 (-07:00)
Reproduction Steps:
I can only seem to be able to reproduce this for one group in particular.
Here are some of the packages affected (should be private to the development team):
ReplicatedFirstFramework
SharedFramework
ClientFramework
CAssetsFramework
I also have server-side package links attached in a private message.
These are the repro steps, except that they only seem to work for the DataSpring Studios group in particular:
- Create a folder in ReplicatedStorage
- Publish this folder as a package, and set the ownership to a group to DataSpring Studios
- Save a file with this package included (or publish a place), and then close this place
- Create a new place, import the package, and make changes.
At this point, pay attention to the “VersionNumber” property, as well as “Status”. It should say “Up-To-Date” after publishing these changes.
- Close the new place without saving, and re-open the place that was saved earlier
Go into ReplicatedStorage, and look at the package. There will be no “Get Latest Package” prompt, and the VersionNumber will be outdated. However, the status will say “Up To Date.” If you delete and re-insert the package, it will fetch the latest version, but that requires a lot of manual effort.
Here’s a place file with out-of-date packages from two groups. Both are empty folders, but the package from DataSpring Studios will not check for updates:
OutOfDateRepro.rbxl (21.4 KB)
Expected Behavior:
I would expect there to be a “Get Latest Packages” prompt when right clicking these packages and an icon showing a new version available for both packages.
Actual Behavior:
I only see the icon showing a new version available for one package (the “Test” package owned by Horrific Games), and nothing for the “CAssetsFramework” Package owned by DataSpring Studios
DataSpring Studios Package:
CAssetsFramework
Horrific Games Package:
Package Bug Test
Workaround:
No workaround. I’m starting to think I’ll have to create an entirely new group to fix this issue.