Bug 13323 - Xamarin Studio stuck at "Waiting for debugger to connect" when trying to debug a app which is not valid due to the 24 hour restriction
Summary: Xamarin Studio stuck at "Waiting for debugger to connect" when trying to debu...
Status: RESOLVED NOT_ON_ROADMAP
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 4.0.10
Hardware: PC Mac OS
: --- normal
Target Milestone: master
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2013-07-18 14:50 UTC by Bo Pang
Modified: 2013-07-23 13:52 UTC (History)
2 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 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 NOT_ON_ROADMAP

Description Bo Pang 2013-07-18 14:50:42 UTC
You should using Trail or Starter license to reproduce this bug.

1. Create a new iOS project from the template.
2. Build and debug the project on a device.
3. Set the date in the device two day after today.
4. Debug project on the device.

Result:  Xamarin Studio Stuck at "Waiting for debugger to connect".
Comment 1 Jeffrey Stedfast 2013-07-22 11:57:42 UTC
Rolf: how can we detect that this won't run?
Comment 2 Rolf Bjarne Kvinge [MSFT] 2013-07-22 11:59:18 UTC
Doesn't the app show a message explaining why it won't start up?
Comment 3 Jeffrey Stedfast 2013-07-22 12:05:17 UTC
I meant so that we don't show the waiting to connect dialog
Comment 4 Rolf Bjarne Kvinge [MSFT] 2013-07-22 13:20:21 UTC
You could check the timestamp of the executable (foo.app/foo), and if it's 24h old and the current license is Trial or Starter+Debug, then show a message.

For this particular case this fix won't work (since the date on the device was modified), but imho that's a fairly strange use-case (strange enough to rely on the message on the device).
Comment 5 Jeffrey Stedfast 2013-07-23 13:50:08 UTC
so is this NOTABUG? The only thing we can realistically do here is reduce the timeout from 2 minutes down to something more like maybe 1 minute?
Comment 6 Rolf Bjarne Kvinge [MSFT] 2013-07-23 13:51:37 UTC
IMHO it's not a bug. I wouldn't even bother modifying the timeout.
Comment 7 Jeffrey Stedfast 2013-07-23 13:52:33 UTC
ok