Bug 37007 - App Freezes on Resume after Sleep
Summary: App Freezes on Resume after Sleep
Alias: None
Product: iOS
Classification: Xamarin
Component: Debugger ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2015-12-15 05:14 UTC by Cody Beyer (MSFT)
Modified: 2017-06-15 10:04 UTC (History)
7 users (show)

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:

Description Cody Beyer (MSFT) 2015-12-15 05:14:31 UTC
### Description

The following app demonstrates an issue where an app will fail to resume after sleep

### Sample


### Steps to Reproduce

1. Download sample
2. Deploy to iOS Device
3. Sleep device
4. Wake Device

### Expected Results

App is responsive

### Actual Result

App is unresponsive 

### Versions

=== Xamarin Studio ===

Version 5.10.1 (build 6)
Installation UUID: 17ea749b-4dee-43b5-afaa-5925246add77
	Mono 4.2.1 (explicit/6dd2d0d)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 402010102

=== Xamarin.Profiler ===

Not Installed

=== Apple Developer Tools ===

Xcode 7.2 (9548)
Build 7C68

=== Xamarin.iOS ===

Version: (Business Edition)
Hash: 7322991
Branch: master
Build date: 2015-12-08 16:20:29-0500

=== Xamarin.Android ===

Version: (Business Edition)
Android SDK: /Users/codybeyer/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		4.0.3 (API level 15)
		4.4   (API level 19)
		6.0   (API level 23)

SDK Tools Version: 24.4.1
SDK Platform Tools Version: 23.0.1
SDK Build Tools Version: 23.0.1

Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

=== Xamarin Android Player ===

Version: 0.6.5
Location: /Applications/Xamarin Android Player.app

=== Xamarin.Mac ===

Version: (Business Edition)

=== Build Information ===

Release ID: 510010006
Git revision: 0b60eecdb531933734519c13257d16a780274aab
Build date: 2015-12-04 20:28:20-05
Xamarin addins: 9876fd7c9837977178411ec7375b4352c0a0d6af
Build lane: monodevelop-lion-cycle6-baseline

=== Operating System ===

Mac OS X 10.11.2
Darwin Codys-MacBook-Pro.local 15.2.0 Darwin Kernel Version 15.2.0
    Fri Nov 13 19:56:56 PST 2015
    root:xnu-3248.20.55~2/RELEASE_X86_64 x86_64
Comment 1 Andy Hopper 2016-02-03 21:40:14 UTC
Would it be possible to get an update on this? We reported this issue a month ago complete with sample code demonstrating the issue and we have seen no activity. To be frank, it is making us look pretty foolish for having chosen Xamarin, especially after the team paid for the highest-priced subscription that supposedly had the best tech support options.
Comment 2 Paul DiPietro [MSFT] 2016-02-09 19:35:38 UTC
This only seems to occur when the debugger is attached. Running the app without it does not cause the error, so I'm reassigning it under iOS which can be adjusted as needed.
Comment 3 Andy Hopper 2016-02-09 19:39:05 UTC
I can assure you that the hang occurs regardless of whether the debugger is attached or not.
Comment 4 Rolf Bjarne Kvinge [MSFT] 2016-02-10 13:06:23 UTC
How do you determine responsiveness if the test app doesn't contain any UI elements that respond to touch? The only thing I could do was to rotate the device, and the app rotated just fine.

In any case could you force-crash the app when it turns non-response [1], and attach the corresponding (symbolicated) crash report?

[1] http://stackoverflow.com/a/30382930/183422
Comment 5 Sebastien Pouliot 2016-04-12 15:47:24 UTC
We have not received further information and will assume this is not an issue anymore. If you can still affected by this please re-open the bug and include the requested information. Thanks.
Comment 6 Chris Cavanagh 2017-02-08 06:28:24 UTC
Cody / Andy - Did you resolve this?  I've been seeing a similar issue...
Comment 7 Dhiren Sarup 2017-06-15 10:04:42 UTC
I faced a similar issue on Mono Android when network socket related objects were being used along with AndroidGameView for OpenGL rendering, and no user action was performed on the OpenGL view for 150 seconds.

A workaround to the problem was dispatching a dummy touch event to the OpenGL view after a fixed duration of say 5 - 10 seconds in a timer.