Lastly, create a symbolic link from our existing install to the Android Studio app directory with "sudo ln -s $SDK_DIR. For me, this is achieved by "cd /Applications/Android\ Studio.app/"īackup the sdk directory that comes with Android Studio by running "sudo mv sdk sdk-bak" Navigate to the Android Studio install directory, and enter the app. When done, just quit the java app (CMD-Q in the window, or CTRL-C from the terminal) This is necessary as Android Studio needs the current version to run. Use the popup to update to the newest version of the tools. Navigate to $SDK_DIR/tools via "cd $SDK_DIR" In my case, this is ~/Engineering/SDKs/android-sdk-macosxĠ. I'll use $SDK_DIR to mean the root of your current SDK installation. This seems rather silly to me (why re-download all the system images?), so here is how to fix it, at least on a Mac: I'm at a loss on where to go with this as there seems to be little information out there on where to go next.I've just gotten around to playing with the new Android Studio today, and the very first thing I found was that it houses its own version of the SDK.
I've removed all Android Studio registry entries.I've tried uninstalling Android Studio.There are plenty of examples of when further information is posted after the "Error running adb:" bit including no device, adb not installed, etc., but nothing that is an empty error message. Upon doing so I now get the error Couldn't start project on Android: Error running adb:Īfter lots of searching the internet I cannot find any other reference to this specific error. Go to the command line and hit expo start wait for the initialisation and then hit a
General workflow is to open the emulator and make sure it is up and running. I'm not even 100% sure how this error started but I am unable to run my project on an emulator at the moment.
0 kommentar(er)
