Search Issue Tracker
Won't Fix
Won't Fix in 3.3.X
Votes
1
Found in [Package]
2.4.0
Issue ID
HUBX-476
Regression
No
[Hub] Menu bar appears and developer tools become available after launching a second instance of Unity Hub
How to reproduce:
1. Open Unity Hub and leave it running
2. Create a new Windows user and switch to it
3. Open Unity Hub while signed in as the user created in step 2
Expected results: Unity Hub window doesn't have a menu bar
Actual results: Unity Hub launches with a menu bar at the top of the window and developer tools become available
Reproducible with: 2.4.0
Notes:
-When launching the second instance of Hub, an "EADDRINUSE: address already in use :::39000" error is logged
-The issue also appears when Hub encounters any other major connection error and fails to reach the servers
-The sign in window becomes blank since Hub is essentially offline
-The issue is also reproducible on macOS
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
- Getting a deprecated package for JetBrains Rider pop up when opening or creating a project
- [Android] Volume level of the same audio file is different on Samsung Galaxy Tab A8 between 2023.3.0b3 and 2023.3.0b4
- ‘Expected end of value’ warning occurs when a property declaration includes five or more variable references
- Crash on BurstCompilerService::CompileAsync when entering Play mode in a specific scene
- InvalidOperationException when using Game Camera Preview in Scene window with a custom RenderGraph pass
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (3.3.X):
(Win 10, Hub 3.1.2) Partially Reproducible, Cannot be tested - Unable to reproduce precise issue, but able to reproduce sub-issue. Sub-issue causes Hub to crash on second user, so first issue cannot be tested.