Search Issue Tracker
In Progress
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
3
Found in
6000.0.47f1
6000.1.0f1
6000.2.0a9
6000.3.0a1
6000.4.0a1
Issue ID
UUM-103996
Regression
No
Licensing Client fails to launch when opening Unity Hub (licensing client path is not found)
Reproduction steps:
1. Open the Unity Hub
2. Observe the Unity Hub
Expected result: Unity Hub opens
Actual result: Unity Hub fails to open
Reproducible with: 1.17.0
Reproducible on: Windows 10 (by the user), Windows 11(24H2) (by the user)
Notes:
-Not reproducible by CQA
-For this exact scenario the following error lines should be present: {{{}Failed to launch licensing client: licensing client path is not found:{}}}, {{Failed to start Unity Hub, reason: LICENSING_CLIENT_CONNECTION_ERROR: Failed to establish a connection with the Licensing Client}}
-A potential workaround involves performing a clean reinstallation of Unity Hub by first backing up the editors-v2.json file. Then, delete all files located in Users/[username]/Library/Application Support/UnityHub (for macOS users) or C:\Users[username]\AppData\Roaming\UnityHub (for Windows users). Afterward, reinstall Unity Hub and restore the editors-v2.json file to its original location
----
The next release of Hub 3.15 contains a fix to mitigate this error, once the 3.15 GA is released publicly, we will monitor user reports to evaluate the efficiency of the fix.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment