Search Issue Tracker
By Design
Votes
0
Found in
2020.3.2f1
2020.3.22f1
2021.2
2022.1
Issue ID
1380566
Regression
Yes
[Packman] Custom Packages do not have Preview/Experimental tag when they're in the Preview/Experimental version
How to reproduce:
1. Create a new project
2. Open the Package Manager
3. In the Package Manager press +->"Add package from git URL..."
4. Add a custom preview/experimental Package (1380566_Custom Package link is in the Edit to use)
Expected results: The Package has Preview or Experimental tag
Actual results: The Package does not have a Preview or Experimental tag
Reproducible with: 2020.3.2f1, 2021.2.8f1, 2022.1.0b2
Not reproducible with: 2019.4.35f1, 2020.3.1f1, 2020.2.7f1
Note:
- In versions 2020.3 and up it can cause an additional problem as there's a warning in the top right of the Editor warning the user about Preview/Experimental Packages being used in the project while the Package Manager does not have tags on the Preview/Experimental Packages causing confusion
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Resolution Note:
This is by design. Custom packages are considered as 'work in progress'. The Experimental tag is reserved for published packages.