Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
0
Found in
2019.4
2020.2
2021.1
2021.2
2021.2.0a1
Issue ID
1299834
Regression
No
[Packman] packages-lock.json file is overwritten when resolving packages
How to reproduce:
1. Create and open a new project
2. Open the Packages folder and observe the Date Modified value of the packages-lock.json file
3. Open the Package Manager window in the Editor
4. Click the refresh icon in the Package Manager window and select Manual Resolve
5. Open the Packages folder
Expected results: the Date Modified value of the packages-lock.json file hasn't changed since packages haven't changed
Actual results: the Date Modified value of the packages-lock.json file has changed
Reproducible with: 2019.4.16f1, 2020.2.0f1, 2021.1.0a10, 2021.2.0a1
Could not test with: 2018.4.30f1
Notes:
-This issue is most prominent when using version control, such as Perforce since this issue causes the packages-lock.json to get checked out
-The same issue can be reproduced by dirtying the manifest.json file and causing a resolve operation this way
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
- Warning "Unable to load Unity.Android.Gradle's referenced assembly NiceIO ..." when recompiling scripts
- "InvalidOperationException: Trying to SetRenderAttachment on a texture..." exception is thrown when using the depth back buffer as an input attachment in Renderer Feature on Vulkan Graphics API
- [HDRP Wizard] Reload Window fails to reload the HDRP Wizard window
- [HDRP Wizard] Fix All button is not presented using the macOS system
- "InvalidCastException: Specified cast is not valid" is thrown when Generating Lighting with "Virtual Offset" enabled in APV, and a static Skinned Mesh Rendered with a Mesh Filter Component is in the Scene
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a7
Resolution Note (fix version 2021.1):
Fixed in 2021.1.2f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.2f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.24f1