Search Issue Tracker
Fixed
Fixed in 3.6.0-beta.1
Votes
0
Found in [Package]
3.1.2
Issue ID
HUBX-780
Regression
No
Typo in the error message when the Hub encounters a critical error
How to reproduce:
1. Install Unity Hub in the default location
2. Create a new project on a BitLocker encrypted drive while it is unlocked
3. Close Unity and Unity Hub, and exit Unity Hub in the system tray. Verify
that Unity Hub is not running in Task Manager.
4. Lock the BitLocker encrypted drive, either by restarting the computer or
running the following command in an administrator command prompt:
manage-bde.exe -lock D:
(replace D: with your drive letter; if it's in use, adding -ForceDismount will
override that, but may cause problems with other applications using the
drive)
5. Attempt to launch Unity Hub
6. Observe the critical error
Expected result: The error says: "The Hub has encountered an..."
Actual result: The error says: "The Hub as encountered an..."
Reproducible with: 3.1.2
Reproducible on: Windows 10
Note: The steps are mostly taken from case HUBX-757
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Warnings in the Bug Reporter window are cut off and not truncated when the Bug Reporter window is resized to its minimum size
- Color is incorrectly applied to objects when initialized with non-normalized parameters
- SerializationUtility.GetManagedReferencesWithMissingTypes() don't return null when “Prefab has missing SerializeReference Types“ warning banner is present
- Memory leak when VFX Graph is open and Camera has "Target Texture" enabled
- The Canvas component's warning box is missing an apostrophe when Additional Shader Channels is set to "Normal" and "Tangent" with Render Mode set to "Screen Space - Overlay"
Add comment