Split View Controller not as a Root View Controller

Question

I have an app that requires user to LOG IN. Once user is logged in, I want to use Split View Controller to display data. The trick is, that Apple doesn't want me to push the SplitViewController, since they want it to be the Root View Controller. From my point of view, it is okay, but I need the user to log in first.

Anybody knows any workaround except creating my own SplitViewController-like VC?

Brett Gregson · Answer 1 · 2012-10-12T08:17:10.630

1

UISplitViewController *svc = (UISplitViewController*)[self.storyboard instantiateViewControllerWithIdentifier:@"SplitView"];
[self presentModalViewController:svc animated:YES];

Assuming you are using storyboards, and have given the split view controller an identifier (SplitView)

edited Oct 12 '12 at 08:17

answered Oct 11 '12 at 15:12

Brett Gregson

5,867
3
42
60

When I do this the app crashes: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Application tried to present a Split View Controllers modally' – Bocaxica Oct 28 '13 at 10:45

score 1 · Answer 2 · edited Aug 28 '13 at 10:47

You can always add a dummy viewController and push the splitView controller on the dummyView Controller and then push the DummyView Controller on top of your present view controller e.g.

AppDelegate *appdelegate = (AppDelegate*)[UIApplication sharedApplication].delegate;
self.splitViewController = [[[UISplitViewController alloc] init] autorelease];
self.splitViewController.viewControllers = @[masterNavigationController, detailNavigationController];
self.splitViewController.delegate = detailViewController;
UIViewController *dummyView = [[UIViewController alloc]init];
[dummyView.view addSubview:self.splitViewController.view];
[appdelegate.rootNavigationController setNavigationBarHidden:YES animated:NO];
[appdelegate.rootNavigationController pushViewController:dummyView animated:YES];

LOL! Looks nice, what a hack haha :-) – Michal Aug 28 '13 at 11:42 — Michal, Aug 28 '13 at 11:42

score 1 · Answer 3 · answered Jan 16 '14 at 09:32

This helped for me (via Xamarin):

public override bool ShouldPerformSegue (string segueIdentifier, NSObject sender)
    {
        if (segueIdentifier != ReportSettingsSegue)
            return base.ShouldPerformSegue (segueIdentifier, sender);

        bool isOk = ProcessLogin (); 
        var svc = (ReportSplitViewController)Storyboard.InstantiateViewController ("ReportSplitViewController");
        View.Window.RootViewController = svc;

        return isOk;
    }

Segue perform after pressing "log in" button on my app's first screen.

Also you must set split controller identifier ID (Storyboard ID) in identity inspector in storyboard (for me it is ReportSplitViewController)

score 0 · Accepted Answer · answered Oct 11 '12 at 15:09

0

You can still change the root view controller if you need to. You can initially set the root view controller to show your login screen, and then replace it with the split view controller. Alternatively, you could present your login screen modally over the top of the split view controller.

answered Oct 11 '12 at 15:09

Mike Weller

45,401
15
131
151

2

This is a nice idea, but from iOS8 and up, presenting a new screen on top doesn't seem to be 'instant', so it'll show you the splitscreen for a moment and then the login on top, which is just plan ugly. – Kevin R Jun 10 '15 at 10:55

Split View Controller not as a Root View Controller

4 Answers4

Linked