rotation - Rotating iPhone 6 Plus results in gray detail view controller? -

I'm experiencing a strange problem with split-scene controllers, and I think this issue is very easy in a brand The new app is redone if you see the iPhone 6 Plus on the Landscape Master and the Expansion View Controller on the screen, rotate, but if you move back to the portrait again and switch tabs, then rotate the scenario, expand the view Control Fully will be gray, if nothing is logged to the console: & lt; Error>: CGImageCreate: Invalid Image Size: 0x0 I would like to know if you can cause the cause or what can be done to fix this bug

<. p> setup with a UITabBarController three tabs, each tab is pulled out through the default UISplitViewController Interface Builder. Change the sub-class UISplitViewController and 3 partition views of that class. Set viewDidLoad itself divided representatives of view controller then from splitViewController Yes Return: CollapseSecondaryViewController: onPrimaryViewController: . This set up is visible after seeing the master default view after rotating the portrait instead of the controller.

To regenerate the bug: Launch the app in the image on iPhone 6 Plus, rotate in the scenario, turn back on the portrait, tap on the second or third tab, To rotate in the scenario, Bug: view the detail controller is completely gray Expected: The detail view controller should appear as if you normally launch the app Tap a different tab, then the scenario Rotate

Additional details: Once the visit to happen, if you Portrait rotate back and then go back to a different tab and a gray detector controller Landscape on rotation Will also show. The app should be left forcibly and in the scenario it should be relaunched to see those split scenes.

Now I saw if you open the app and the first tab is displayed, if you want to rotate the iPhone 6 Plus into the landscape, it is actually a tab bar controller (5 additional view controllers) The owner and extension initiates the view controller - this prevents the breakpoint set in the viewDidLoad , if you sub-class those controllers, I expected that the split view displayed on the screen Only the detail view for Yntrk controller must initialize. I am thinking that this is the candidate's behavior? I believe this can be linked to this bug.

My question is, is this a gray screen bug in iOS, or there is a problem with this setup, or is it Can something be done to prevent it from happening?

How should it look:
< / P>

How it looks when adheres to the above steps:

While working on my sample, I found myself feeling something strange . I was actually showing 2 table views in the 6+ simulator instead of 1 table view and 1 detail view. I can recover it by returning my details view controller in the form of the separateSecondaryViewControllerFromPrimaryViewController

My code is like this:.

  function splitViewController (splitViewController: UISplitViewController, different Sekenderiwukantrolrframri ViewController primary ViewController: UIViewController!) - & gt; UIViewController? {If the primary ASN Integrator = Provided to the Primary View Controller? UINavigationController {If the top ASTiL VIPU controller = Primary ASNV controller. If given to the TETWeek controller? } Return null}  

be used

me it was only when TableView2 TopViewController, so I'm initialising DetailViewController'm checking it and really if I my mind and return it .

Hope this vision You also work for angles.