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.
I’m struggling with an issue when I use a DateTime object.
Every time I use a DateTime object my app crash on my iPhone 5 and iPhone 4.
On the simulator and on a iPhone 5s device it works correctly.
My Code looks as follows:
public override void ViewDidLoad ()
DateTime myDateTime = DateTime.Now;
string dateAsString = myDateTime.ToString ();
In XCode i get the error: Exception Type: EXC_BAD_ACCESS (SIGSEGV).
I attached a sample project.
Created attachment 6193 [details]
DateTime Demo project which crashs on iPhone 5 / 4
Do you live/use a Swiss German region on your device? [bug #17690]
If not, please attach the crash report (you can get the crash report from Xcode's Organizer), and any device log output (which you can find in Xamarin Studio's menu View -> Pads -> iOS Device Log).
Created attachment 6195 [details]
iOS Log from Xamarin Studio
Created attachment 6196 [details]
Log from XCode
Thank you for your fast response :)
Yes i live in a Swiss German region
I attached both logs. i found an interesting line in the log:
the local store doesn't allow tasks and we have no default calendar :(
So this is a duplicate of bug #17690.
The bug has been fixed, but we haven't released it yet. Bug #17690 lists a few workarounds people have used in the meantime.
*** This bug has been marked as a duplicate of bug 17690 ***