Bug 42658 - App crashing xamarin_initialize when load storyboard
Summary: App crashing xamarin_initialize when load storyboard
Status: RESOLVED NORESPONSE
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: master
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Sebastien Pouliot
URL:
Depends on:
Blocks:
 
Reported: 2016-07-19 14:15 UTC by Luca
Modified: 2016-11-11 16:11 UTC (History)
3 users (show)

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


Attachments
Crash log I Found on iPhone 6 (39.81 KB, text/rtf)
2016-07-19 14:15 UTC, Luca
Details


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:
Status:
RESOLVED NORESPONSE

Description Luca 2016-07-19 14:15:58 UTC
Created attachment 16714 [details]
Crash log I Found on iPhone 6

Hi all,

It seems Mono runtime crash at app start. It not happens always and not in all device I can test.

I attach the log I found in the device (in insight there is nothing). The class reported in log (CustomNavController) is defined as:

    using System;
    using UIKit;
    using Foundation;

    namespace TouristApp {
	
    [Register ("CustomNavController")]
    public class CustomNavController : UINavigationController {

		public CustomNavController(IntPtr handle) : base(handle) { }
		public CustomNavController() { }

		public override UIInterfaceOrientationMask GetSupportedInterfaceOrientations () {
			return  TopViewController.GetSupportedInterfaceOrientations ();
		}

		public override bool ShouldAutorotate () {
			return TopViewController.ShouldAutorotate ();
		}
	}
    }

This extended UINavigationController is call in Storyboard file.

Version of Xamarin studio, ios and Mono are up to date to the last stable version.
Comment 1 Rodrigo Kumpera 2016-07-19 21:30:21 UTC
The app is dying with an unhandled exception in the binding engine.
Comment 2 Luca 2016-07-20 06:57:26 UTC
Thx for the reply. I do not understand: it is a problem of my app or a bug of Xamarin.iOS?
Comment 3 Rodrigo Kumpera 2016-07-20 06:58:29 UTC
Could be either, I'm letting the Xamarin.iOS figure this out.
Comment 4 Rolf Bjarne Kvinge [MSFT] 2016-07-20 08:17:17 UTC
Please get the device log as well (from Xamarin Studio: menu View -> Pads -> iOS Device Log) from a crash, that will give more information about the exception that occurred.
Comment 5 Luca 2016-07-20 10:35:33 UTC
I'm sorry I have only the log of the app. On the device I uninstall and reinstall the app and it works, so I cannot reproduce the crash on the same device.
In both case it is a fresh install of the app.

As I said it happens a few times and not on all device.
Comment 6 Rolf Bjarne Kvinge [MSFT] 2016-07-20 10:38:43 UTC
This could be an issue where the app wasn't built properly, so the exception you're seeing would be because the storyboard was missing/incorrect, but without more details about the exception it's impossible to diagnose further.

So could you get the device log if you run into this again?
Comment 7 Luca 2016-07-20 10:52:20 UTC
Of course next time I try to get also the device log. Thanks for the support. Could you leave this bug report open?
Comment 8 Rolf Bjarne Kvinge [MSFT] 2016-07-20 10:53:46 UTC
Yes, we can leave it open for a while.
Comment 9 Sebastien Pouliot 2016-11-11 16:11:47 UTC
We have not received any additional information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!