Search Issue Tracker
By Design
Votes
0
Found in
6000.0.44f1
6000.1.0b12
6000.2.0a7
Issue ID
UUM-100907
Regression
No
Some deprecated packages are seen in "Unity Registry"
How to reproduce:
1. Create a new Unity project
2. Go to Window -> Package Management -> Package Manager (Window -> Package Manager)
3. Go to "Unity Registry"
4. Look for "Lobby", "Matchmaker", "Multiplay", "Relay" or "ML Agents"
5. Observe the results
Expected results: Deprecated packages can't be found
Actual results: Deprecated packages can be found
Reproducible with: 6000.0.44f1, 6000.1.0b12, 6000.2.0a7
Can't test with: 2022.3.60f1 (These packages are not deprecated)
Reproducible on: macOS Sequoia 15.3 (M1)
Not reproducible on: No other environment tested
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
The visibility of the Unity registry packages is controlled by the editor manifest file which is managed by the release managers. The file can be found under: Unity.app > Contents > Resources > Package Manager > Editor > manifest.json
You will notice all the deprecated packages mentioned in the bug description are part of the _isDiscoverable_ packages from the editor manifest.