Search Issue Tracker
Fixed in 2019.2.X
Votes
0
Found in
2019.2.0a7
Issue ID
1131602
Regression
No
Packman UI - Disabling Modules error message is inaccurate
When the user attempts to disable a module through the Package Manager UI, the error message shown to him is erroneous in displaying references to "remove" instead of "disable".
Steps to reproduce:
- Start Unity and open Package Manager UI
- In the Package scope drop-down menu, select Built-in packages
- In the list find and click on VR built-in package
- On the bottom right side of the Package specific detail view press the button "disable"
Notice that there is a pop-up menu that appears with three buttons:
- The title says: "Removing Package". Expected text would be "Disable Package"
- The description says: "Are you sure you wanted to remove this package?". Expected text would be "Are you sure you wanted to disable this package?". Also notice that "wanted" should be corrected to "want".
- The left most button says: "Remove and do not ask again". Expected text would be "Disable and do not ask again"
- The right most button says: "Remove". Expected text would be "Disable"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment