Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
1
Found in
2022.2.0a16
Issue ID
UUM-2317
Regression
No
Packages are not immutable when they are imported as tarballs
Reproduction steps:
1. Download the attached tarball package "test.tgz" and import it into any project
2. In the Editor, open any of the imported package's scripts from the Project window
3. Edit the script and save changes to it
4. Return to Unity to recompile the scripts
5. Inspect the edited script again
Expected result: The script returns to its previous state
Actual result: The changes to the script are saved
Reproducible with: 2019.4.39f1, 2020.3.35f1, 2021.3.4f1, 2022.1.3f1, 2022.2.0a15
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note:
This behaviour is intended to be phased out for packages installed from a registry or a Unity installation files (built-in) as it introduces performance and usability concerns; instead, users should be able to decide when they want to revert a package to its original state (of course, this implies users need to be able to *know* when a package is not in its original state). As a result, the underlying mechanism will not be extended to tarballs.
Resolution Note (2022.2.X):
This behaviour is intended to be phased out for packages installed from a registry or a Unity installation files (built-in) as it introduces performance and usability concerns; instead, users should be able to decide when they want to revert a package to its original state (of course, this implies users need to be able to *know* when a package is not in its original state). As a result, the underlying mechanism will not be extended to tarballs.