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
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.
The message is specific to iOS and should be updated for Mac.
Aside: I didn't even notice this message because it scrolled by too quickly due to all the other logging in my app. As a result I spent about an hour reading headers and searching for examples before figuring it out (thanks to finding bug #23474 via Google and inquiring about it internally). It would be super nice to somehow make this (and other similar situations) more obvious. Maybe a long sleep (gross) or an NSAlert (slightly less gross?).
I am trying to reproduce this issue but not sure about the steps. Could you please provide us test case or test sample project? So that I can reproduce this issue at my end.
@Danish, no need for you to reproduce this, I know what the problem is.