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.
Dear Lazy Xamarin Employees
I have lodged bug report 24098, and despite my meticulous efforts to provide you detailed instructions and source code to reproduce the issue, your lazy and incompetent staff have claimed the issue does not exist and simply decided to ignore it.
TRY TESTING IT IN LANDSCAPE MODE YOU FUCKING DEADSHITS
The real bug appears not so much to be in the software of Xamarin, but in the psychology of Xamarin who think they charge insane prices for BUG RIDDLED shit and simply ignore bug reports.
You are not an open source outfit anymore but a HIGHLY PRICED enterprise market ISV - start acting like one.
It's not the job of your ripped off paying customers to test and fix your bug riddled crap.
Now, go fix issue 24098 you fucking fat lazy morons.
Apologies for the inconvenience caused.
As per the steps provided in the Bug 24098 I have observed that this issue exists only on the release mode with the Landscape orientation.
So I have updated the Bug 24098 with the more detailed information and changed the status to Confirmed. Now the developer will look into it and will get back to you as soon as possible.
As of now I am marking this issue as the Duplicate of the Bug 24098 and will close it once the original issue get fixed.
*** This bug has been marked as a duplicate of bug 24098 ***