Search Issue Tracker
Fixed
Votes
0
Found in [Package]
Issue ID
1260550
Regression
Yes
Packages added in manifest.json Scoped Registry do not get listed in the Package Manager
How to reproduce:
1. Create a new Unity project
2. Open the project's manifest.json externally
3. Add a package scoped registry entry before the dependencies section
4. Refocus Unity and open the Package Manager
5. Look for the added package
Expected result: package appears in the list of packages
Actual result: package does not appear in the list of packages
Reproducible with: 2020.1.0a15, 2020.1.0b15, 2020.2.0a16
Not reproducible with: 2019.4.3f1, 2020.1.0a14, 2020.2.0a17
Could not test with: 2018.4.24f1(tested package incompatible with this version)
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
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
Resolution Note:
Fixed in 2020.2.0a17
Packages now appear in a separate Package Manager section, accessed by the dropdown: 'Packages: My Registries'