Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 11062 [details]
Using the default Xamarin.Android empty template in VS2015 RC, in Release mode, the following error message appears on the device LogCat :
monodroid-debug: Error communicating with the IDE, exiting...
This happens with any kind of device or emulator. Does not happen in debug build.
See attachment for version details.
I have checked this issue and unable to reproduce the above behavior given in the bug description. When I run Xamarin.Android empty template in VS2015 RC,in Release Mode it deploy successfuly and no error message found in device LogCat.
Device Logs: https://gist.github.com/saurabh360/bd2a4fdc60dd5512c117
Microsoft Visual Studio Enterprise 2015 RC
Version 14.0.22823.1 D14REL
Microsoft .NET Framework
Installed Version: Enterprise
Architecture and Modeling Tools 00269-30000-00001-AA617
Microsoft Architecture and Modeling Tools
UML® and Unified Modeling Language™ are trademarks or registered trademarks of the Object Management Group, Inc. in the United States and other countries.
LightSwitch for Visual Studio 2015 RC 00269-30000-00001-AA617
Microsoft LightSwitch for Visual Studio 2015 RC
Visual Basic 2015 RC 00269-30000-00001-AA617
Microsoft Visual Basic 2015 RC
Visual C# 2015 RC 00269-30000-00001-AA617
Microsoft Visual C# 2015 RC
Visual C++ 2015 RC 00269-30000-00001-AA617
Microsoft Visual C++ 2015 RC
Visual F# 2015 RC 00269-30000-00001-AA617
Microsoft Visual F# 2015 RC
Windows Phone SDK 8.0 - ENU 00269-30000-00001-AA617
Windows Phone SDK 8.0 - ENU
Application Insights Tools for Visual Studio Package 1.0
Application Insights Tools for Visual Studio
ASP.NET and Web Tools RC 14.0.20417.0
ASP.NET and Web Tools RC
ASP.NET Web Frameworks and Tools 2013 5.2.30411.0
For additional information, visit http://www.asp.net/
Common Azure Tools 1.4
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.
Generates unit test code for methods in classes under test.
Microsoft Azure Mobile Services Tools 1.4
Microsoft Azure Mobile Services Tools
Microsoft Code Digger 0.9
Microsoft Code Digger
NuGet Package Manager 3.0.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.
Office Developer Tools for Visual Studio 2015 RC ENU 14.0.22523
Microsoft Office Developer Tools for Visual Studio 2015 RC ENU
SQL Server Data Tools 14.0.50325.0
Microsoft SQL Server Data Tools
Workflow Manager Tools 1.0 1.0
This package contains the necessary Visual Studio integration components for Workflow Manager.
Xamarin 3.11.445.0 (5061f92)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android 126.96.36.199 (d23da369e436488f38c8ab8fe8a9ae7d9ea5256b)
Visual Studio plugin to enable development for Xamarin.Android.
Xamarin.iOS 188.8.131.52 (7741cc495ab0baf04ff0405d0604bc27f0ecae2e)
Visual Studio extension to enable development for Xamarin.iOS.
Xamarin.iOS Unified Migration 1.0
Automated migration for Xamarin iOS Classic projects to Unified
Early preview of Xamarin Test Cloud integration
I'm running on Windows 10, also.
Would the APK be useful ?
@Jerome: The problem is that "something" has set the debug.mono.connect system property (the debugger or the profiler), but didn't clear that property. That property is checked at startup to determine whether to attempt to connect to the IDE/profiler/etc., and if it *can't* connect it exits.
I'm starting to wonder if that "exit if it can't connect" behavior is actually desirable. :-/
Regardless, clearing the debug.mono.connect system property should fix the problem, e.g. by rebooting the device or with:
adb shell setprop debug.mono.connect ''
*** This bug has been marked as a duplicate of bug 29485 ***
Thanks Jonathan !
Actually, providing a more explicit message on why this happens could be more interesting.
Something like "Error communicating with the IDE, exiting. Check if the value of debug.mono.connect is correct".