Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
0
Found in
2018.4
2019.3.15f1
2019.4
2020.1
2020.2
Issue ID
1263378
Regression
No
[Packman] Package Manager resolver asks for writable access when opening a project even though it only needs readable access
How to reproduce:
1. Download the attached "1263378 repro.zip" project
2. Open "manifest.json" and "packages-lock.json" files from the Packages folder and observe that they are empty
3. Select "manifest.json" and "packages-lock.json" files in the Packages folder
4. In the right-click menu click Properties and make both files Read-only
5. Open the project with a newer version of Unity than the one provided
Expected results: Package Manager resolver doesn't ask for writable access to "manifest.json" and "packages-lock.json" files
Actual results: Package Manager resolver asks for writable access to "manifest.json" and "packages-lock.json" files
Reproducible with: 2018.4.25f1, 2019.4.5f1, 2020.1.1f1, 2020.2.0a19
Notes:
-This issue can also be reproduced with default project packages
-Package Manager resolver usually doesn't modify these files after giving it writable access
-Usually, the Package Manager resolver actually modifies these files only when installing the "com.unity.ide.visualstudio" package in newer versions of Unity
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
- Profiler - Taking you to the wrong section when using 'show'
- Draw Renderers custom pass doesn't work with SSGI
- WebCamTexture does not set the requested resolution when used in WebGL
- Editor default Stylesheet/Matching Selector buttons in Debugger don't do anything
- Graphics.DrawMeshNow stops rendering Render Texture after a few frames when viewed in the Player
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a1
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0b12
Resolution Note (fix version 2020.3):
Fixed in 2020.3.5f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.22f1