Bug 29895 - Debugging on iOS device - Visual Studio hangs when iOS times out the application
Summary: Debugging on iOS device - Visual Studio hangs when iOS times out the application
Status: RESOLVED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Debugger ()
Version: 3.11 (C5)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Joaquin Jares
URL:
Depends on:
Blocks:
 
Reported: 2015-05-08 19:31 UTC by Alina Popa
Modified: 2017-05-31 18:37 UTC (History)
4 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 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 Alina Popa 2015-05-08 19:31:40 UTC
When debugging an application on iOS device, iOS may kill the application if is too slow (with "failed to launch in time" or "failed to scene-update in time". When this happens, Visual Studio does not know that the application was terminated, and it freezes. When attempting to press any button in Visual Studio, the following message may pop out: "Visual Studio is waiting for an internal operation to complete". That internal operation never completes.
Comment 1 Enzo Heredia 2016-04-11 16:48:50 UTC
are you still seeing this behaviour in latest alpha build?
Comment 2 Joaquin Jares 2017-05-31 18:37:39 UTC
This looks like it's fixed now. I'm marking as fixed for verification. Please reopen if you're still seeing the issue.