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.
Created attachment 4994 [details]
I am currently porting an existing iOS 6 app to iOS 7 and am facing some strange behaviour when values passed to a new instance of a view controller by constructor are not available on ViewDidLoad().
This seems only to happen when the controller called is a sub class of another controller which accesses the TableView in its own constructor.
See a failing test attached.
I am currently on 18.104.22.168 (Hash: 4cfca2f, Build date: 2013-20-09 23:14:32-0400).
This is normal.
Accessing TableView in DetailBaseDialog.ctor will end up calling ViewDidLoad, so you end up in DetailDialog's ViewDidLoad method before its ctor has been executed.
That's not the behaviour I would expect here. But ok.
Conceptually it's the equivalent to this: https://gist.github.com/rolfbjarne/8c9d4598d8e9ec2c511e, since Objective-C calls ViewDidLoad when you fetch the TableView property.
Okay. The strange thing about that is, that it worked until I switched to iOS 7.
What probably happened is that iOS doesn't call ViewDidLoad when fetching the TableView property in previous versions.