Compatibility and check Migrate to a physical computer with a different processor version. Your building process will be terminated without closing the emulator and then press debug button again, your app will be deployed. If you still cannot deploy the app especially those who stuck at (AppName).Android -> (Path)\bin\Debug(AppName).Android.dll, try to press ctrl+break in VS. Let me rexplain with more detail.įor those who cannot find HKEY LOCALMACHINE\SOFTWARE\WOW6432Node\Android SDK Tools, please create Android SDK Tools key yourself and then create a String Value named Path with value C:\Program Files (x86)\Android\android-sdk (Please verify if this path is same as yours). Thanks supplement on solution for those do not find the key in regedit. Deployment is successful this way but you still need to start and run the installed app yourself. I just started the emulator via AVD and then deployed the solution from Build > Deploy Solution. I find my Android SDK's path from VS > Tools > Options > Xamarin > Android SDK Location. I didn't have 'Android' key in HKEY LOCALMACHINE\SOFTWARE\Wow6432Node, so I created myself. So I created it and added a New String value with Value name: "Path" and Value data: "C:\Program Files (x86)\Android\android-sdk" which matched with the path to my Android SDK folder. Sorry, i'm not allowed to post links yet.īasically what posted, but for me the "Android SDK Tools" folder didn't exist. Restart the emulator and you should now be able to see the emulator connected to ADB and associated Android tools. Modify the Path registry variable to match the path to your Android SDK. Navigate to HKEY LOCALMACHINE\SOFTWARE\Wow6432Node\Android SDK Tools in the folder tree on the left. Open Registry Editor by selecting Run from the Start buttons context menu, typing regedit in the dialog box, and choosing OK. To modify the Android SDK path used by the emulator: The emulator uses a registry key to identify the base location of your Android SDK, and looks for the \platform-tools\adb.exe file under that directory. If the emulator is running, but it does not appear to be connected to ADB (Android Debug Bridge) or it does not appear in Android tools that make use of ADB (for example, Android Studio or Eclipse), you may need to adjust where the emulator looks for ADB. Visual Studio gets stuck trying to deploy the app to the emulator or the emulator does not appear as a debug target in other IDEs that I found at Microsoft's troubleshooting page under section:
At that point you can make any changes to your app and redeploy as many times as you need without the need of launching the emulator every time.Īnd additionally I needed a permanent fix. VS debugger will stop as soon as the app gets removed from the emulator. You can leave the emulator running all the time. Once you are done testing your app, make sure you uninstall it again. (Your emulator Android version and API level need to be equal or greater than the Target Framework in your app's android manifest).Īfter that you will see how your app gets deployed to the emulator.
Select the emulator in VS that matches the one already running, and click the button to start building and deploying your app. Go to the Apps section in the emulator (circle with little dots) and make sure you uninstall your application from the emulator.Īfter that, open VS and load your solution. I noticed in the VS IDE Output window that a message was coming as - not enough disk space.Īfter increasing the SD card and recreating the emulator that you want to use, launch the emulator independently using Android SDK Tools -> AVD Manager. In your emulators, make sure that the SD Card size in the emulator's configuration is big enough. In Visual Studio do Ctrl-Alt-O to show the output window so you can see any error popping up during emulator launch and app deployment.
#Can't start android emulator on mac install#
I removed any standalone installation of Xamarin and used only what Visual Studio Installer offers to install Xamarin (mobile cross-platform development for.
#Can't start android emulator on mac windows 10#
I tried all suggestions above but in my case none of them work.Īfter some more troubleshooting I was able to figure it out on Windows 10 home edition.
0 kommentar(er)
