Bug 18165 - Debugger provides no information on exception that occurs when missing a permission
Summary: Debugger provides no information on exception that occurs when missing a perm...
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Debugger ()
Version: 1.12.x
Hardware: PC Windows
: High normal
Target Milestone: ---
Assignee: dean.ellis
Depends on:
Reported: 2014-03-04 13:56 UTC by Roger Peters
Modified: 2016-05-10 16:57 UTC (History)
6 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 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 Roger Peters 2014-03-04 13:56:16 UTC
In a Xamarin University course (AND102) we show the user how the app will crash if we try to launch a phone call action intent without having the uses-permission to make phone calls in their app manifest. When showing this exception occur, I get no details on the crash, just a big gray dialog. There is a marker at least pointing to the line where the exception occurred, and you can find the exception printed out in the debug window, but it is not showing exception details as expected.

You find details on this issue posted on the forum with no resolution:

While that user was using VS2012, I am using VS2013, however the issue is the same. 

To recreate the issue, add a button and button handler, call this code (without adding any permissions) and see that the exception popup matches the photo in the forum thread:

// make phone call
var callIntent = new Intent(Intent.ActionCall);
callIntent.SetData(Android.Net.Uri.Parse("tel:" + translatedNumber));
Comment 1 dean.ellis 2014-06-05 08:31:58 UTC
I've managed to replicate this. Trying to figure out how to fix it.
Comment 3 dean.ellis 2014-06-12 10:57:27 UTC
Fixed in XamarinVS/master/948f1da156