Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.0a8
Issue ID
1024540
Regression
No
Packages in the editor manifest are automatically marked as Verified in X, even if they haven't been verified
If a package is added to the editor manifest, it is always marked as "Verified in x" in the Package Manager UI. This will lead to situations where say, a beta version of the editor is released including packages that are yet to be verified, but they will still be marked as such in the UI. There needs to be a way to include packages in the editor manifest without them being marked as "Verified in x" in the Package Manager UI.
1. Download and install Unity
2. Look in the packages included in editor manifest
2. Open the Package Manager UI
3. Scroll through the packages from the editor manifest
4. All packages are marked as "Verified in X"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Add comment