Bug 43110 - Crash in navigation
Summary: Crash in navigation
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 6.0.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Future Cycle (TBD)
Assignee: Bugzilla
Depends on:
Reported: 2016-08-06 10:57 UTC by Jens Engelbrecht
Modified: 2016-09-09 11:39 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Logfiles (272.27 KB, text/rtf)
2016-08-06 10:57 UTC, Jens Engelbrecht

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Jens Engelbrecht 2016-08-06 10:57:54 UTC
Created attachment 16927 [details]

Crashes when loading a new view
Comment 1 Alex Soto [MSFT] 2016-08-09 06:03:11 UTC
Unfortunately that crash log attached is not symbolicated and it is not enough to determine what is going on.

Please include your full build logs, symbolicated crash reports, 
a test case (to reproduce) and all version informations.

The easiest way to get exact version information is to use the 
"Xamarin Studio" menu, "About Xamarin Studio" item, "Show Details" 
button and copy/paste the version informations (you can use the 
"Copy Information" button).
Comment 2 Vincent Dondain [MSFT] 2016-09-09 11:39:38 UTC
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report.