Note that there are some explanatory texts on larger screens.

plurals
  1. POSegue from NavigationBarItem to UINavigationViewController
    primarykey
    data
    text
    <p>I have a tutorial and at the end of the tutorial I want to push from a UIViewController to a UINavigationViewController. I need the UINavigationViewController because I'm using <a href="https://github.com/edgecase/ECSlidingViewController" rel="nofollow">ECSlidingViewController</a> . The view which is managed by this UINavigationViewController is a UITableViewController. Okay so far everything is easy to understand right? No problem. But now it gets weird. Now I use this code (IBAction):</p> <pre><code>HomeNavViewController *home = [[HomeNavViewController alloc] init]; [self presentModalViewControllerhome animated:YES]; </code></pre> <p>Everything I get is an app termination from the debugger. Does anyone have experienced this already?</p> <p>Thanks in advance for any help :)</p> <p>Here is the error message (sorry I forgot to post it in the first place :) ):</p> <pre><code>2013-05-14 16:43:07.313 187ers[1124:c07] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSArrayM insertObject:atIndex:]: object cannot be nil' *** First throw call stack: (0x2c3e012 0x210be7e 0x2bf1b6a 0x2bf1a20 0x2aca3f 0xeac4 0x340103 0x34042b 0x34df80 0x54a223 0x346ee3 0x347167 0x3471a7 0xe4cc 0x211f705 0x2602c0 0x49ca64 0x211f705 0x2602c0 0x260258 0x321021 0x32157f 0x3206e8 0x28fcef 0x28ff02 0x26dd4a 0x25f698 0x2b99df9 0x2b99ad0 0x2bb3bf5 0x2bb3962 0x2be4bb6 0x2be3f44 0x2be3e1b 0x2b987e3 0x2b98668 0x25cffc 0x2e4d 0x2d75) libc++abi.dylib: terminate called throwing an exception (lldb) </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload