Search Issue Tracker
Fixed
Votes
19
Found in
2018.2.11f1
2018.2.15f1
2018.3.0b2
2019.1.0a8
Issue ID
1100382
Regression
Yes
[Linux] Mac Support is only pseudo-installed through Hub for Linux Editor
To reproduce:
1) Open Unity Hub
2) Go to Installs and check the menu of "Add Component
3) If Mac support is not installed, install it
4) Note that Mac support is installed and checked there
5) Open a new project on the version that you checked
6) Go to Build Settings
Expected: You can switch to Mac support
Actual: There is no option for that. Equally so, when opening a project in the advanced selection, Mac support is not detected there either
Reproduced in 2018.2.10f1, 2018.2.11f1, 2018.2.15f1, 2018.3.0b2, 2018.3.0b8, 2019.1.0a8
Not reproduced in 2018.2.7f1
-
vishnuramguru
Aug 28, 2020 16:37
Even though I installed the Mac Support and Windows Support in Unity Hub, I cannot switch the platform. I have no Mac or Windows drop-down while switching! It only shows Linux(I am using Ubuntu 20.04)
-
vincentgravitas
Mar 19, 2020 22:00
Still present in Unity Hub 2.3.0. Please fix this......
-
mosaic_school
Sep 27, 2019 10:56
Still the case for Unity-Hub 2.1.2 and the Unity-Editor 2019.2.
-
artics
Dec 28, 2018 13:37
Still exist in Hub 1.4
Crutch solution: https://forum.unity.com/threads/cant-build-mac-os-x-target-on-linux-ubuntu-18-04.586255/ -
artics
Dec 28, 2018 13:37
Still exist in Hub 1.4
Crutch solution: https://forum.unity.com/threads/cant-build-mac-os-x-target-on-linux-ubuntu-18-04.586255/
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
- No space between checkbox and text in UI Toolkit Project Settings
- Dynamic Atlas Viewer has a different multiple choice dropdown
- Value of the "OnApplicationFocus" is "True" when Player loses the focus before it launches
- .mp3 playback position is inaccurate when loaded with .streamAudio while in Play Mode
- DateTime.Now returned time is 1 hour behind when system time zone is set to Morocco
Resolution Note:
Fixed with the release of Hub 2.3.1