UITableViewController should call the designated initializer of UIViewController

Originator:steipete
Number:rdar://20549233 Date Originated:15-Apr-2015 10:04 AM
Status:Closed Resolved:
Product:iOS SDK Product Version:8.3
Classification:Other Bug Reproducible:Always
 
Summary:
UITableViewController calls [super init] inside initWithStyle:. This breaks the designated initializer chain and prevents subclasses from blocking e.g. initWithNibName:bundle: from being called.

Expected Results:
UITableViewController should call [super initWithNibName:bundle:] inside initWithStyle:.

Actual Results:
UITableViewController calls [super init] inside initWithStyle:, which then calls [self initWithNibName:bundle:]. This results in the overridden [self initWithNibName:bundle:] being called, which might be overridden to prevent direct calls to it, resulting in a crash/assertion.

Regression:
This has always been a bug but with the SDK 8.3 changes has become more visible.

Notes:
See http://petersteinberger.com/blog/2015/uitableviewcontroller-designated-initializer-woes/ for details.

No sample project necessary, but since I know that there are people pushing back if there is no code attached to a radar, I’ve added a simple Sample project that asserts when running - but should work correctly if thus bug is fixed.

Comments

Fixed in iOS 9.

By steipete at June 8, 2016, 8:32 p.m. (reply...)

Sample: http://cl.ly/043Y1z3q2k0h

By steipete at April 15, 2015, 8:09 a.m. (reply...)

Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!