Search Unity

Builds immediately failing with "Unity is not available at expected path"

Discussion in 'Unity Build Automation' started by MigrantP, Oct 20, 2021.

  1. MigrantP

    MigrantP

    Joined:
    Jun 24, 2013
    Posts:
    119
    We have had builds randomly failing since yesterday with the following error. It seems like there's a build machine or two that are missing the Unity version we're building with?

    Unity is not available at expected path: /UNITY_PATH/Unity/macos/published/Unity-2019_4_28f1/Unity.app/Contents/MacOS/Unity. The version you are attempting to use has likely been deleted. Please update your settings, or contact support if this is unexpected.

    The full log:
    1: Running Prebuild steps
    2: In quiet period, build will start momentarily...
    3: Using /BUILD_PATH/.rvm/gems/ruby-2.4.2
    4: Successfully uninstalled bvr-2.0.9
    5: Successfully uninstalled bvr-3.0.13
    6: Successfully uninstalled bvr-3.0.25
    7: Successfully uninstalled bvr-3.0.35
    8: Successfully uninstalled bvr-3.0.56
    9: Successfully uninstalled bvr-3.0.71
    10: Removing bvr
    11: Removing bvr_runner
    12: Successfully uninstalled bvr-3.6.3
    13: Unity is not available at expected path: /UNITY_PATH/Unity/macos/published/Unity-2019_4_28f1/Unity.app/Contents/MacOS/Unity. The version you are attempting to use has likely been deleted. Please update your settings, or contact support if this is unexpected.
    14: Build failed. Please check the log for further details.
    15: Using /BUILD_PATH/.rvm/gems/ruby-2.4.2
    16: postbuildsteps finished successfully
    17: postbuildstatus finished successfully.
    18: Finished: FAILURE
     
    ayama9tlr215 and rodrigor_unity like this.
  2. ayama9tlr215

    ayama9tlr215

    Joined:
    Dec 22, 2018
    Posts:
    2
    We are running into the same error recently. It's been happening since October 20th, as we see from the build history. We are using Unity 2019.4.28f1, just like MigrantP does. It seems like it fails 30% of the cases.

    Log:
    1: Running Prebuild steps
    2: In quiet period, build will start momentarily...
    3: Using /BUILD_PATH/.rvm/gems/ruby-2.4.2
    4: Successfully uninstalled bvr-2.0.9
    5: Successfully uninstalled bvr-3.0.13
    6: Successfully uninstalled bvr-3.0.25
    7: Successfully uninstalled bvr-3.0.35
    8: Successfully uninstalled bvr-3.0.56
    9: Successfully uninstalled bvr-3.0.71
    10: Removing bvr
    11: Removing bvr_runner
    12: Successfully uninstalled bvr-3.6.3
    13: Unity is not available at expected path: /UNITY_PATH/Unity/macos/published/Unity-2019_4_28f1/Unity.app/Contents/MacOS/Unity. The version you are attempting to use has likely been deleted. Please update your settings, or contact support if this is unexpected.
    14: Build failed. Please check the log for further details.
    15: Using /BUILD_PATH/.rvm/gems/ruby-2.4.2
    16: postbuildsteps finished successfully
    17: postbuildstatus finished successfully.
    18: Finished: FAILURE
     
  3. MigrantP

    MigrantP

    Joined:
    Jun 24, 2013
    Posts:
    119
    @ayama9tlr215 - I got in touch with Unity support about this, and they implemented a workaround for us - a manual override so our builds go to machines that are known to work. Feel free to reference this thread and our ticket number 1120106 if you contact support.
     
    ayama9tlr215 likes this.
  4. ayama9tlr215

    ayama9tlr215

    Joined:
    Dec 22, 2018
    Posts:
    2
    @MigrantP It seems to be working fine now. Thanks for that!