Bug 27622 - Reporting a Java.IO.IOException to Insights permanently blocks the calling application.
Summary: Reporting a Java.IO.IOException to Insights permanently blocks the calling ap...
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 5.2
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Gord Allott
Depends on:
Reported: 2015-03-03 21:45 UTC by Matthew Robbins
Modified: 2017-06-28 16:18 UTC (History)
4 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 Matthew Robbins 2015-03-03 21:45:01 UTC
When providing a Java.IO.IOException to Xamarin.Insights via Report(...), the application will permanently lock while it attempts to serialise the exception.

This causes extremely serious unexpected behaviour; I've experienced this causing both a deadlock and an ANR.

The bug occurs in Insights version 1.8.2 and earlier.

This small sample reproduces the issue:
namespace InsightsCrash
	[Activity (Label = "InsightsCrash", MainLauncher = true, Icon = "@drawable/icon")]
	public class MainActivity : Activity
		int count = 1;

		protected override void OnCreate (Bundle bundle)
			base.OnCreate (bundle);

			// Set our view from the "main" layout resource
			SetContentView (Resource.Layout.Main);

			// Get our button from the layout resource,
			// and attach an event to it
			Button button = FindViewById<Button> (Resource.Id.myButton);
			button.Click += delegate {

				try {
					Java.IO.File f = new Java.IO.File("borkeded/file.path");
					Java.Lang.StringBuilder sb = new Java.Lang.StringBuilder();
					Java.IO.BufferedReader br = new Java.IO.BufferedReader(new Java.IO.FileReader(f));
				} catch (Java.IO.IOException ex) {

					const string ANALYTICS_INSIGHTS_APIKEY_DEVELOPMENT 	= "my-key";
					Xamarin.Insights.Initialize(ANALYTICS_INSIGHTS_APIKEY_DEVELOPMENT, this.BaseContext);
					Xamarin.Insights.Report (ex);
Comment 1 Jon Douglas [MSFT] 2017-06-28 16:18:41 UTC
As per the announcement of Insights joining HockeyApp, I am marking this bug as RESOLVED INVALID for the time being:



If this issue is still present in HockeyApp, please feel free to reopen this issue.