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.
Hi Guys, I am have a strange problem - I just updated to the newest update and is working in xamarin studio mac version 5.4(240).
In of of my classes I have the following code:
if (string.IsNullOrEmpty(Password) || string.IsNullOrEmpty(Username)
Password and Username are property strings and no matter what it always evaluate true. If both have values it still says true. Its very frustrating as none of my code is working af the update.
I need to update my bug report I ony have the problem in monodroid and visual studio - the same code work fine in mac and ios.
Sorry for the spam. The code work on mono droid on mac as well. So the issue is isolated to monodroid and visualstudio in windows - please do write if you need for more info.
I believe that I have made a mistake. It seems that the debugger led me to believe that issue was in that if sentence. However the subsequent code was executed but resulted in an error. Some datetime calculation which has worked for the past year suddenly stopped working. and gave an argument out of range exception. I needed to change the code from:
var seventies = new DateTime (1970, 1, 1);
var time = DateTime.UtcNow - seventies.ToUniversalTime ();
var epoch = new DateTime(1970, 1, 1, 0, 0, 0, DateTimeKind.Utc);
var d = DateTime.UtcNow.Subtract (epoch);
That's due fixed bug. The new behaviour is correct one.