Bug 5271 - MonoDevelop cannot interact with emulators with the latest android tools
Summary: MonoDevelop cannot interact with emulators with the latest android tools
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Add-in ()
Version: Trunk
Hardware: PC Mac OS
: Normal major
Target Milestone: ---
Assignee: Alan McGovern
URL:
: 5270 ()
Depends on:
Blocks:
 
Reported: 2012-05-23 05:47 UTC by Alan McGovern
Modified: 2014-04-04 20:11 UTC (History)
5 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Alan McGovern 2012-05-23 05:47:23 UTC
If you install the following, MonoDevelop will no longer be able to deploy to emulators:

Android SDK Tools: rev 19
Android SDK Platform-tools: rev 11

You just get the error message ": can't find sdkmanager.jar" printed to the terminal every time you try to start an emulator.
Comment 1 Alan McGovern 2012-05-23 05:47:43 UTC
This issue has been reproduced by Jeremie aswell
Comment 2 Alan McGovern 2012-05-23 06:03:59 UTC
This is just a regression in MonoDevelop/master. The 3.0-series branch works just fine. This is not a particularly critical issue, so downgrading it again. It's a lot less severe than I anticipated.
Comment 3 PJ 2012-06-13 13:37:01 UTC
*** Bug 5270 has been marked as a duplicate of this bug. ***
Comment 4 Mikayla Hutchinson [MSFT] 2014-04-04 20:11:07 UTC
This is no longer an issue.