Search Issue Tracker

In Progress

Fixed in 2023.2.16f1, 2023.3.X

Fix In Review for 2021.3.37f1, 2022.3.23f1



Found in







Issue ID




[Android] Editor terminates the ADB connections when an emulator is running in Android Studio



Reproduction steps:
1. Open the attached project "PROJECT_PATH"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Open “PROJECT_PATH2“ in Android Studio
4. In Android Studio, select any emulator and press the “Run” Button
5. In Editor, open the Preferences window (Edit > Preferences)
6. Select the External Tools tab
7. Make sure all Android modules are installed with Unity
8. Change the Android SDK Module to use Android Studio’s SDK
9. Change the Android SDK Module back to SDK installed with Unity
10. Open the Build Settings window (File > Build Settings)
11. Click the Refresh Button next to the “Run Device” option
12. Repeat steps 4 - 11 for about 5 times

Expected result: The Editor does not terminate ADB connections
Actual result: The message “Multiple ADB server instances found, the following ADB server instance has been terminated due to being run from another SDK“ appears in the Console window

Reproducible with: 2021.3.32f1, 2022.3.12f1, 2023.2.0f1, 2023.3.0a16

Reproducible on: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested

- Forum thread of the same issue: [|]

  1. Resolution Note (fix version 2023.3):

    There will be a new option Preferences->External Tools->Kill External ADB instances.

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.