Bug 37742 - Xamarin.Insights support could not be added to your project due to an error
Summary: Xamarin.Insights support could not be added to your project due to an error
Status: RESOLVED DUPLICATE of bug 27758
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Insights Add-in ()
Version: 5.10 (C6SR3)
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: master
Assignee: Greg Munn
URL:
Depends on:
Blocks:
 
Reported: 2016-01-16 00:01 UTC by Joe Mellin
Modified: 2016-01-19 17:56 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
The second error message (332.25 KB, image/png)
2016-01-16 00:01 UTC, Joe Mellin
Details


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 DUPLICATE of bug 27758

Description Joe Mellin 2016-01-16 00:01:13 UTC
Created attachment 14605 [details]
The second error message

I was creating a xamarin forms project in XS and I got this error message after an error message that said "Untrusted Certificat detected" => insights.xamarin.com
Comment 1 Greg Munn 2016-01-18 22:31:47 UTC
Is this still an issue Joe? I was getting certificate errors from the updater at the same time. I don't think there is much I can do with that error.
Comment 2 Joe Mellin 2016-01-19 17:50:23 UTC
it doesn't seem to be an issue anymore.   Would be good to know the underlying cause of it.
Comment 3 Greg Munn 2016-01-19 17:56:34 UTC
as far as I can tell, it's similar to #27758

*** This bug has been marked as a duplicate of bug 27758 ***