0

The picture says it all.

I have tried opening the emulator in the avd manager and access it through the run menu without success.

Background info: - I recently upgraded to MacOS High Sierra. - I have updated Android Studio to 3.0 Beta 7 trying to solve the issue. - The commands "emulator" and "avd" are unrecognized commands now. - I am also using react-native, accessing the emulator from react-native run-android and android studio too, doesn't work anymore.

enter image description here

ben_lize
  • 107
  • 9

2 Answers2

0

If the project API matches you emulator API version and emulator is running try restarting ADB. In Android studio - Tools -> Android -> Enable Adb integration and then once again to turn it on. Or 

adb kill-server
adb start-server
kodlan
  • 561
  • 8
  • 23
  • So is your emulator running? – kodlan Oct 04 '17 at 11:56
  • The emulator is running. Still, the devices listed in the adb should mirror in the run screen as usual and I cannot load my app into it through Android Studio. – ben_lize Oct 04 '17 at 12:01
  • Check in your build.gradle file if the targetSDK and minimumSdk version is lower or equal to the sdk version of your Emulator. – kodlan Oct 04 '17 at 12:03
  • To test I have made a new project with min version API 15 and still cannot see the 6 emulators that should be appearing. – ben_lize Oct 04 '17 at 12:09
  • I've deleted all Android Studio an app from my Macbook, re-installed, created a new project, a new emulator and still same issue. – ben_lize Oct 04 '17 at 12:35
0

This helped me get my adb devices back in sync with Android Studio. It was an adb port problem at root.

" I finally resolved my issue, it occurs if you run java and ADB at the same time.

to fix it stop all java processes in the activity monitor.

shareeditflag answered Mar 10 at 20:25

Joran Dob 163114 " ADB in android studio keeps showing same error message and does not start

ben_lize
  • 107
  • 9