Bug 55418 - Xamarin Android deploys in VS2017 hang
Summary: Xamarin Android deploys in VS2017 hang
Status: RESOLVED NORESPONSE
Alias: None
Product: Android
Classification: Xamarin
Component: Debugger ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-04-20 02:53 UTC by Katelyn Gadd
Modified: 2017-08-23 21:07 UTC (History)
3 users (show)

Tags: bb
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 NORESPONSE

Description Katelyn Gadd 2017-04-20 02:53:23 UTC
Under normal circumstances if I try to debug a Xamarin Android project using VS2017, the deploy process hangs right after this:

1>XASRESymbolTest -> e:\Documents\Projects\XASRESymbolTest\bin\Debug\XASRESymbolTest.dll
1>  Processing: obj\Debug\res\layout\main.xml
1>  Processing: obj\Debug\res\values\strings.xml

When I examine a procmon log, VBCSCompiler.exe has finished updating the dll and mdb files, but everything is just stuck. Even killing processes won't recover it.

There are two workarounds:

a) Nuke the entire contents of the bin/ folder so that the application is recompiled from scratch. This results in jar signing, keytool, etc all happening and then the emulator starts and the app is deployed.

b) Start a debug, then cancel the build after the deploy hangs. *Leave that emulator instance open*, then try to debug again. This time the deploy will succeed.

So some combination of 'existing application binary' and 'starting new emulator instance from scratch' causes the deploy process to silently hang. I haven't been able to figure out how to troubleshoot this further.

For context, I installed VS2017 community from scratch this morning and then asked it to install Xamarin for me. This occurs using the Android 'Single-View App' template with no changes. I'm using the VisualStudio_android-23_x86_phone (Android 6.0 - API 23) emulator option.
Comment 1 Mark McLemore 2017-06-23 18:36:39 UTC
Hi, can you attach some additional information to help us reproduce this error (for example, log files and/or a test case)?  Please have a look at: https://developer.xamarin.com/guides/cross-platform/troubleshooting/questions/howto-file-bug/

Thanks!
Comment 2 Cody Beyer (MSFT) 2017-08-23 21:07:29 UTC
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!