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
- Editor crashes and a window with "GetManagerFromContext: pointer to object of manager 'MonoManager' is NULL (table index 5)" error is shown when launching a freshly created project
- Editor Windows dragging behavior is erratic/glitchy when a specific multi-display setup is used and the Editor window is not on the main display
- Meta Quest missing an icon in Build Profiles window in U6.0
- Foldout arrow indent is misaligned in the Inspector when used for Arrays or Lists
- Material import pipeline strips properties when it is added with a script
Add comment