Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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
GitHub or 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.
This is everything that was reporter by Xamarin Insight:
Object reference not set to an instance of an object
I could not reproduce the error and it only happens to people who downloaded our app in the store. Therefore I can't really provide anything helpful to find a solution for this.
Possible duplicate of https://bugzilla.xamarin.com/show_bug.cgi?id=32685?
That's what I thought but the other one is marked as resolved fixed, so this seems to be another reason for the same bug.
Tableau has an app that is hitting this same issue in the store. 400 hits in 30 days. Note this happens on app resume paths.
System.NullReferenceExceptionObject reference not set to an instance of an object
at System.Net.ServicePoint.CheckAvailableForRecycling (System.DateTime& outIdleSince) [0x00000] in <filename unknown>:0
at System.Net.ServicePoint.IdleTimerCallback (System.Object obj) [0x00000] in <filename unknown>:0
at System.Threading.Timer+Scheduler.TimerCB (System.Object o) [0x00000] in <filename unknown>:0
Properties & Custom Values
*** This bug has been marked as a duplicate of bug 32685 ***