Unity Hub 3.2.0

Bug fixes & improvements

1. Fix

   Downloads and Installations

2. Fix

   We’ve resolved an issue where certain Android modules were marked as installed in the Hub but not detected by the Editor.

   • Android
3. Fix

   When installing new Editor versions, the Hub occasionally presented incorrect Android submodules for download. You'll now see the appropriate submodules.

   • Android
4. Fix

   Project Creation

5. Fix

   If you come across the ‘Project failed to open’ error modal, you’ll now see a link to the logs folder so that you can quickly view the info-log.json for troubleshooting or to send to support.

6. Fix

   Some users reported that they could not create a project if it had "[x]" in the name (where x is a one-digit number or letter). You can now do this without an issue.

7. Fix

   User Interface

8. Fix

   When choosing modules to install with an Editor, you can now click anywhere on the row to select instead of having to click the checkbox.

9. Fix

   Text in various areas of the Hub wasn't displaying correctly and was accidentally cut off. We’ve corrected this.

10. Fix

    Visual Studio

11. Fix

    Previously, Visual Studio appeared as uninstalled, even if it had been, when you attempted to install a different Editor version. This has been fixed.

12. Fix

    We’ve fixed a connected download issue between the Visual Studio and Documentation module when one or the other fails.

13. Fix

    The Hub now recognizes the installation state of Visual Studio when downloading an Editor through the archive, so you do not have to reinstall it.

14. Fix

    In some cases, if Visual Studio failed to install, it also caused all other modules to fail. We’ve fixed this issue.

15. Fix

    Windows

16. Fix

    Those on Windows reported that the ‘hovering state’ was not displayed when you hovered over the minimize, maximize, and close buttons. This has been fixed.

    • Windows
17. Fix

    macOS

18. Fix

    Users on macOS reported an issue that prevented the PATH environment variable from being correctly provided to the Editor. This has now been resolved.

    • macOS
19. Fix

    On macOS, some users reported that when a new editor install failed, it did so without notifying them. We have now added a message to let you know if this happens.

    • macOS
20. Fix

    We’ve fixed a bug on macOS that resulted in IL2CPP clang processes running as Intel on Apple silicon machines when using an Apple silicon editor. They will now run natively.

    • macOS