Search Issue Tracker
Fixed in 2019.4.X
Fixed in 2020.1.X, 2020.2.X
Votes
0
Found in
2019.3.15f1
2019.4
2020.1
2020.2
Issue ID
1263361
Regression
No
Package manager doesn't ask if manifest.json and packages-lock.json files should be made writable when opening a project
How to reproduce:
1. Download the attached "1263361 repro" project
2. Open "manifes.json" from the Packages folder
3. Change "com.unity.timeline" version from 1.2.14 to 1.2.15 and save the file
4. Select "manifest.json" and "packages-lock.json" files in the Packages folder
5. In the right-click menu click Properties and make both files Read-only
6. Open the project
Expected result: UPM asks if the user would like to make the required files writable in order to resolve the conflict
Actual result: resolving the packages fails without an option to make the files writable
Reproducible with: 2019.4.5f1, 2020.1.0b16, 2020.2.0a18
Could not test with: 2018.4.25f1 (the packages-lock.json doesn't exist)
Notes:
-When upgrading the project to a newer Unity version UPM asks whether it should make the files writable in order to resolve packages as expected
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Player build freezes after calling Application.Quit() when the scripting backend is set to IL2CPP
- Texture is not applied on a Custom Render Texture when a Cubemap is selected as the texture
- 2D light leaks through ShadowCaster2D when ShadowCaster2D components are disabled then re enabled at runtime in Player builds
- Unity Hub redirects to The Unity Roadmap when navigating to “Send Feedback” option
- UI Toolkit throws warning and fails to clear references when fields are not typed as UnityEngine.Object
Add comment