Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
Issue ID
1046915
Regression
No
When installing a new package, Package Manager does not default to installing the most recent version of the package.
Steps to reproduce:
- Download Unity Editor version 2018.2.0b8
- Open the package manager.
- Change to the "All" tab and look at the Post-processing package.
Expected:
When installing a package to a project for the first time, it should install the most recent version of the package.
Observed:
For the Post-processing package, it defaults to try to install 0.1.8, but the most recent version is 2.0.7-preview. See attached screenshot in the comment below
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Add comment