Skip to content

Get-UnitySetupInstance can't find some of installed unity versions on mac #208

Open

Description

@yvz-dmr

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.

image

Activity

  1. MaxGuernseyIII commented on Jul 29, 2020

    @MaxGuernseyIII

    I'm experiencing this with 2020.1.0f1 installed via this package.

  2. MaxGuernseyIII commented on Jul 29, 2020

    @MaxGuernseyIII

    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?

  3. mister-liss commented on Jan 11, 2021

    @mister-liss

    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'

    image

  4. mister-liss commented on Jan 14, 2021

    @mister-liss

    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'

    image

    I was able to resolve this by updating UnitySetup, duh.

  5. mister-liss commented on Jan 14, 2021

    @mister-liss

    woops, did not mean to close the whole issue

  6. deitry commented on Jun 1, 2022

    @deitry

    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

    if ( Test-Path "$path\modules.json" -PathType Leaf ) {

    ), solution would be to extract Unity version from path itself

  7. yacuzo commented on Jun 14, 2022

    @yacuzo

    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?

  8. dorszpw commented on May 30, 2025

    @dorszpw

    have now the same issue installing Unity 2022.3.36f1 on mac with Components "Mac, iOS"

    Doing the steps:

    Install-Module -Name UnitySetup -Force -AcceptLicense -Verbose
    Install-UnitySetupInstance -Installers (Find-UnitySetupInstaller -Version $unity_version -Components $unity_components) -Verbose
    

    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

    Start-UnityEditor `
      -Credential $credentials `
      -Serial $secure_serial `
      -BatchMode `
      -Quit `
      -Wait 
    
    

    response is

    Image

    Also when running
    Get-UnitySetupInstance -Verbose
    Response is:

    Image

    Get-UnitySetupInstance -BasePath "/Applications/Unity/Hub/Editor/*" -Verbose
    Response is:

    Image

    Any chance to fix that? It blocks using Start-UnityEditor to activate the license, and alternative (ADO extension task) is deprecated now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions