Closed benhysell closed 11 years ago
Do you have a use case for this? Subviews should never be null.
I didn't think they were ever null either, except latest alpha of xamarin with Xcode dp3 crashes without the added null check.
-ben
On Jul 10, 2013, at 10:39 PM, James Clancey notifications@github.com wrote:
Do you have a use case for this? Subviews should never be null.
— Reply to this email directly or view it on GitHubhttps://github.com/Clancey/FlyoutNavigation/pull/27#issuecomment-20786787 .
Yeah, I ran into this in some of my own code. In iOS 7 Beta 3 View.Subviews can sometimes be null. Xamarin has already been addressing it, see: https://bugzilla.xamarin.com/show_bug.cgi?id=13119
This is going to be fixed with the next alpha. So no need for the patch to be commited long term.
Thanks for the pull request though!
You are welcome! Sorry I didn't see this was a bug with the alpha.
Added a null check to prevent crashing on latest iOS and Xamarin builds