Two packages: A and B.
B is inside of A.
When you publish B, then publish A, then update all instances of A, all of the instances of B inside will be unexpectedly marked as modified.
(Also sometimes Update All doesn’t work with no error messages, the modal action button just does nothing).
Expected behavior
The nested package should not be marked as modified after updating A, since B is part of A, and B is up to date in the version of A being fetched.
Thanks for the report! I filed a ticket in our internal database and we’ll follow up when we have an update for you.
Have the same issue. Also some other unexpected behaviors of packages. Folder packages don’t have a pivot so they will be placed in the world space the same in both places. If I copy paste the folder package from one place to another, it doesn’t put it in the same position. If I update the package in the original place, then get latest package in the other place you don’t get the behavior in the original video by PeZsmistic. It moves itself to the correct location, but doesn’t not say the nested packages need an update.
Also if I have the package in the correct world space location and then move it, it says it has been modified which is expected. But then I hit undo changes to package and it moves it back, but then it says all nested packages have been modified when they haven’t been. If you undo the changes to all nested packages, you then get stuck in an endless loop of undoing the nested packaged, then the parent package. Below video demonstrates the OPs bug as well as this other one I just mentioned.
We are using packages to sync the map for our game between places. These bugs make it much more annoying to work with.
This is fixed. Let me know if it’s still happening.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.