You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Get-UnitySetupInstance can't find some of installed unity versions on mac #208
I have installed all versions of unity in my mac via UnitySetup powershell module but it cant find some of them when using Get-UnitySetupInstance. I am using unity setup module version of 5.3.134.
All unity versions are located in same directory which is default unity hub install location. For example unity version 2019.4.0f1 is installed but it isn't listed when calling Get-UnitySetupInstance.
Not sure if this is a seperate bug but might be related. On windows after I installed a 2019 version I started getting the following after Get-UnitySetupInstance and Start-UnityEditor
'Unable to find version for C:\Program Files\Unity\Hub\Editor\2019.4.14f1'
Not sure if this is a seperate bug but might be related. On windows after I installed a 2019 version I started getting the following after Get-UnitySetupInstance and Start-UnityEditor
'Unable to find version for C:\Program Files\Unity\Hub\Editor\2019.4.14f1'
I was able to resolve this by updating UnitySetup, duh.
I recently encountered same and found that Unity installed via Install-UnitySetupInstance (at least 2021.3.0f1) doesn't have modules.json file which is used to "establish" version. Unity installed via Unity Hub have one and didn't have this issue.
With current code (see Get-UnitySetupInstanceVersion content like
I got this on a new build-server with 2021.3.3f1. The old build-server (also installed from these scripts) does not have this issue. Both servers have the same version of the scripts (5.4.130). Any info I can provide you to help out?
The Editor is installed seems properly in /Applications/Unity/Hub/Editor/2022.3.36f1, but then tried to start Unity Editor like below to activate the license
Activity
MaxGuernseyIII commentedon Jul 29, 2020
I'm experiencing this with 2020.1.0f1 installed via this package.
MaxGuernseyIII commentedon Jul 29, 2020
In my case, it's the inability of the system to determine the version number that appears to be the problem. Is that what's happening to you?
mister-liss commentedon Jan 11, 2021
Not sure if this is a seperate bug but might be related. On windows after I installed a 2019 version I started getting the following after Get-UnitySetupInstance and Start-UnityEditor
'Unable to find version for C:\Program Files\Unity\Hub\Editor\2019.4.14f1'
mister-liss commentedon Jan 14, 2021
I was able to resolve this by updating UnitySetup, duh.
mister-liss commentedon Jan 14, 2021
woops, did not mean to close the whole issue
deitry commentedon Jun 1, 2022
I recently encountered same and found that Unity installed via
Install-UnitySetupInstance(at least2021.3.0f1) doesn't havemodules.jsonfile which is used to "establish" version. Unity installed via Unity Hub have one and didn't have this issue.With current code (see
Get-UnitySetupInstanceVersioncontent likeunitysetup.powershell/UnitySetup/UnitySetup.psm1
Line 1247 in 4c4041a
), solution would be to extract Unity version from path itself
yacuzo commentedon Jun 14, 2022
I got this on a new build-server with 2021.3.3f1. The old build-server (also installed from these scripts) does not have this issue. Both servers have the same version of the scripts (5.4.130). Any info I can provide you to help out?
dorszpw commentedon May 30, 2025
have now the same issue installing Unity 2022.3.36f1 on mac with Components "Mac, iOS"
Doing the steps:
The Editor is installed seems properly in /Applications/Unity/Hub/Editor/2022.3.36f1, but then tried to start Unity Editor like below to activate the license
response is
Also when running
Get-UnitySetupInstance -VerboseResponse is:
Get-UnitySetupInstance -BasePath "/Applications/Unity/Hub/Editor/*" -VerboseResponse is:
Any chance to fix that? It blocks using Start-UnityEditor to activate the license, and alternative (ADO extension task) is deprecated now