Open Radar

 
Summary:
When you add a custom inputAccessoryView to the UIViewController, somehow the inputAccessoryView (or a subobject) holds a strong reference to the UIViewController that originated the call. This causes a retain cycle and the View Controller never gets released.

Steps to Reproduce:
1. Create a UINavigation based app
2. Create a UIViewController on the second level of the stack.
3. Assign a custom inputAccessoryView to the UIViewController
> - (BOOL)canBecomeFirstResponder
>{
>    return YES;
>}
>
>- (UIView *)inputAccessoryView
>{
>    return self.accessoryView;
>}
4. Run the app and navigate to that screen
5. Navigate back, to pop the view controller

Expected Results:
The UIViewController should get popped and dealloc after that.


Actual Results:
It's not what happens. - dealloc is never called, and UIViewController remains in Memory.

Version:
iOS 8.0.2

Notes:


Configuration:
iPhone 5s, or Simulator 8.0

Attachments: