Singleton instance already exists. about ios-slide-menu HOT 4 CLOSED

That log means it's assigning the newly created SlideNavigationController to the singleton instance which is already assigned to one. As long as that's what you mean to do it's fine. It's more like a warning.

I personally never kill the login page. I keep it as the first item in the stack, and when signing out is selected i just pop to rootViewController. The demo project does exactly that.

Unfortunately I haven't found any better way to manage a singleton instance in a way that works both in code and storyboard. The reason SlideNavigationController is a singleton is so that you are able to reference it when it's created using initWithCoder, also to be able to easily access it from animator classes and the menuViewController.

I'll probably add a more meaningful message for that in the next version to avoid any confusion.

from ios-slide-menu.

Ok Thank you very much for your explanation, I will take your advice not to kill the login page. it's an amazing controller thank you very much for your support.

from ios-slide-menu.

Just a TLDR & Summary for future reference:

To avoid that warning have SlideNavigationController as the starting point of your storyboard.

from ios-slide-menu.

Im still seeing this warning message. Is there any update?

from ios-slide-menu.