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 21107 [details]
I'm using Visual Studio 2015 Enterprise with Update 3 and the latest stable version of Xamarin (v18.104.22.1685), Xamarin.Android (v22.214.171.124), Java JDK 1.8.0_71, and Android SDK Build Tools 25.0.2. The same issue is present for a colleague of mine who is using Visual Studio 2017.
My Android application builds successfully, and then deploys to the device successfully. However, When the 'Start debugging Android application...' message appears, Visual Studio becomes unresponsive, and hangs at that point indefinitely. The app is on the device at that point and works as expected, but the debugger fails to attach to the process, and doesn't automatically launch the app.
It's worth noting that the issue only started happening after upgrading Xamarin.Firebase.Messaging to v42.1001.0 from v32.961.0. The package has various dependencies which were also updated.
I've attached a .zip of my Xamarin logs from the project (the project name has been replaced with 'XXX'). The final line in the IDE log is the 'running fixup on project' line, but I don't know if that's significant. I'm happy to provide additional information/logs if they are required.
*** This bug has been marked as a duplicate of bug 53817 ***