Search Issue Tracker
Fixed
Fixed in 6000.0.48f1, 6000.2.X
Votes
1
Found in
6000.0.48f1
6000.1.2f1
6000.2.0a10
Issue ID
UUM-104990
Regression
No
Licensing Client fails to launch when opening Unity Hub (ClientAlreadyLaunched - UnsupportedProtocol)
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: {{Process exited with code null for pipe Unity-LicenseClient-USER}} , {{Failed to start Unity Hub, reason: LICENSING_CLIENT_CONNECTION_ERROR: Failed to establish a connection with the Licensing Client }} , {{Failed with ipc error type: UnsupportedProtocol}}
-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
Add comment
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
Resolution Note:
This issue has been fixed in Unity Hub's versions newer than 3.14.3. Upgrading to the latest Unity Hub version resolves the issue.
Resolution Note (fix version 6000.2):
This issue has been fixed in Unity Hub's versions newer than 3.14.3. Upgrading to the latest Unity Hub version resolves the issue.
Resolution Note (fix version 6000.0.48f1):
This issue was outside of the Unity Editor, and users experiencing this issue should update to Unity Hub 3.15 where significant improvements have been made regarding the interactions with the licensing client.