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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.