Search Issue Tracker
By Design
Votes
0
Found in [Package]
3.7.0
Issue ID
HUBX-1018
Regression
No
Unity Hub does not reflect installed modules when using the Hub CLI
Reproduction steps:
1. Open the Unity Hub
2. Install any Editor version with the iOS module
3. Open any Terminal
4. Run the command "\{path/to/unity_hub_executable} -- --headless install-modules --version \{INSTALLED_UNITY_EDITOR_VERSION} --module android"
5. Observe the Unity Hub "Installs" section
Alternate reproduction steps:
1. Open any Terminal
2. Run the command "\{path/to/unity_hub_executable} -- --headless install --version \{UNITY_EDITOR_VERSION} --module ios"
3. Locate the Editor installation in the Unity Hub
4. Run the command "\{path/to/unity_hub_executable} -- --headless install-modules --version \{INSTALLED_UNITY_EDITOR_VERSION} --module android"
5. Observe the Unity Hub "Installs" section
Expected results: The Android module shows up below the Unity Editor version that was specified in the command
Actual results: The Android module does not show up below the Unity Editor version
Reproducible with: 3.7.0
Reproducible on: macOS 14.2 (M1), Windows 11 Pro 23H2
Not reproducible on: No other environment tested
Notes:
- Installing a Unity Editor version through the CLI also does not update the GUI with the installed version
- Restarting the Unity Hub shows the versions and modules installed with the CLI correctly
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
- A memory leak occurs with massive terrain when camera position changes occur.
- No valid hits are returned when using RaycastCommand
- Camera is not overlooking the main Scene in Scene View in the HDRP Sample Template
- TextShadow properties are not applied when displayed in a custom MenuItem Window
- Memory leak occurs when focused on Player while using Direct3D12
Resolution Note:
Unity Hub does not support installation via the CLI while being open