Search Issue Tracker

Fixed in 2019.1

Votes

3

Found in

2019.1.0a13

Issue ID

1113208

Regression

Yes

[Android] IndexOutOfRangeException is thrown when refreshing device list with the build window closed

Deployment Management

-

IndexOutOfRangeException is thrown on switching the platform to Android when Assets are present in the Project

Steps to Repro:
1. Open a new project
2. Make sure you don't have a device plugged into your machine
3. Open android build settings
4. Click on "Refresh" near "Run Device" section
5. Close the build settings window before the refresh is complete
6. Notice the error in the console

In theory, this should also be possible with a device connected, but the refersh is very fast when there's a device. It's a lot slower without one.

Actual Result:
IndexOutOfRangeException error appears in console once Platform is switched

Environment:
Windows Only

Occurring with:
2019.1.0a13

Working with:
2019.1.0a12, 2018.3.0f2

Stack Trace:
IndexOutOfRangeException: Index was outside the bounds of the array.UnityEditor.Android.AndroidBuildWindowExtension.GetBuildPlayerWindow () (at <aaaad43e3ca74cf4bd3aa90120b5daff>:0)UnityEditor.Android.AndroidBuildWindowExtension.RepaintTargetList () (at <aaaad43e3ca74cf4bd3aa90120b5daff>:0)UnityEditor.EditorApplication.Internal_CallUpdateFunctions () (at C:/buildslave/unity/build/Editor/Mono/EditorApplication.cs:200)

Comments (3)

  1. 63df168b552318c0e7e01d6e3d5cb02d?d=mm

    makinahmet

    Mar 05, 2019 22:33

    I have same problem on 2018.3.7f1

    /*********************
    IndexOutOfRangeException: Index was outside the bounds of the array.
    UnityEditor.Android.AndroidBuildWindowExtension.GetBuildPlayerWindow () (at <76abbd884b37447da464288ec1125ab8>:0)
    UnityEditor.Android.AndroidBuildWindowExtension.RepaintTargetList () (at <76abbd884b37447da464288ec1125ab8>:0)
    UnityEditor.EditorApplication.Internal_CallUpdateFunctions () (at C:/buildslave/unity/build/Editor/Mono/EditorApplication.cs:200)
    *****************************/

  2. B61f8f97aed544da5ab9f455cc663f27?d=mm

    Matanpjelly

    Feb 24, 2019 08:40

    i have this issue on all versions of 2018.3.x

  3. 1944610125f4ac41ee16082ec841e745?d=mm

    popoved1975

    Jan 03, 2019 13:21

    I have this error on 2018.3.0f2

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.