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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment