This sounds like a bug with the xamarin side of things, we will continue to investigate but because the bug is not with our code this might take a little longer. Please see the following bug https://bugzilla.xamarin.com/show_bug.cgi?id=2162. It suggest setting some application flags which might help resolve the problem.