Search Issue Tracker

Not Reproducible

Votes

8

Found in

2018.1.0a4

2018.3.0f2

2019.1.0a1

Issue ID

1109409

Regression

Yes

[Freeze] Editor fails to close after using VREditor.SetVREnabledDevicesOnTargetGroup in a batchmode build

Asset - Database

-

Steps to reproduce:
1. Download latest attached project(oc link)
2. Run it through command line:
<PATHTOEDITOR> -batchmode -quit -projectPath <PATHTOPROJECT> -logFile C:\Users\giedrius\Downloads\case_1109409-visualizer\dev\build_logs\build_log_HTCVive.txt -executeMethod Visualizer.Editor.Build.BuildOculus -csv_import
3. If it runs fine, run it again with this command line:
<PATHTOEDITOR> -batchmode -quit -projectPath <PATHTOPROJECT> -logFile C:\Users\giedrius\Downloads\case_1109409-visualizer\dev\build_logs\build_log_HTCVive.txt -executeMethod Visualizer.Editor.Build.BuildHTCVive -csv_import

Expected result: build finishes, batchmode editor closes
Actual result: build finishes but the editor stays open in the processes list (stuck on "Refresh: detecting if any assets need to be imported or removed ...")

Reproduced on 2018.1.0a4, 2018.1.0a6, 2018.1.0a11, 2018.1.0b1, 2018.3.0f2, 2019.1.0a12
Not reproduced in 2017.4.17f1, 2018.1.0a1, 2018.3.0a3
Regression introduced in 2018.1.0a4

  1. Resolution Note:

    This has been fixed by other fixes made in the context of the Asset Import Pipeline V2.
    Checked on 2019.3.16f1 (91f465a473a4), 2020.1.0b11 (de513167607b), 2020.2.0a13 (542ff463470b).

Comments (6)

  1. arjenveenhuizen

    Jun 20, 2019 05:47

    For anyone running into this issue, this is caused by the PckageManager looking for com.unity.xr.oculus.android and not finding it locally. A work-around (tested on 2018.3.0f2 for linux) is to get into your project, make a deepcopy of Packages/com.unity.xr.oculus.android/ and, before you start your BuildPipeline/invoke Unity put the content of this folder again in the right spot. Don't rely on the PackageManager to fix it for you, it will not do it properly for you. Interestingly I still have to do this trick even when I am not using the contents of this package. I switched to the official OVR unitypackage 1.36/1.37/1.38 and removed everything in Packages/com.unity.xr.oculus.android/Plugins to make sure that the OVRPlugin.aar does not clash with OVRPlugin from the former.

    Changing the manifest.json by removing this dependency won't help as it keeps on popping up automatically.

  2. arjenveenhuizen

    Mar 27, 2019 09:14

    We just ran into the exact same issue on 2018.3.0f2 for Linux when creating an Android GearVR build in batchmode.

  3. andersemil

    Mar 08, 2019 09:23

    And it's not just VR, it includes Vuforia AR

  4. andersemil

    Mar 08, 2019 09:17

    Also reproduced in 2018.3.5f1. It means any automated builds are impossible, including UCB.

  5. Carpet_Head

    Jan 10, 2019 16:10

    Reproducible. Breaks out build pipeline

  6. Carpet_Head

    Jan 10, 2019 16:10

    Reproducible. Breaks out build pipeline

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.