New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iOS 8 error: adding a root view controller UITabBarController as a child of view #476
Comments
I have problems on iOS8 too, probably ViewDeck is ready for retirement :( |
Same. Any thoughts on a good replacement? I've tried NVSlideMenuController, but it's also pretty buggy. |
I switched to MMDrawerController a while ago. Steady updates and support - I also had no problems under iOS6,7 or iOS8 with it. |
The problem is that I feel that IIViewDeckController has outgrown my ability to spend time on it. It is also too bloated. I might do new a swift implementation for fun, but it will be much more lean. |
Inferis - try adding some key people as contributors to your master branch. |
Oh, I'd love to do that. The trouble is: finding people to take over. I've asked before, but got no response. |
Ah, nice. Sure, that could be arranged. |
I also got this bug. Have you guys got any solutions? |
Hi, I am the new maintainer since @Inferis is not able to maintain this project. Is this bug still relevant? If so, could someone please exactly describe steps to reproduce, as I don't see any issues with this at the moment. I am also thinking about dramatically reducing the feature set of ViewDeck on a 3.0.0 release in the future to be able to support this more easily. I would be very happy if everyone could provide as much feedback as possible about what features you are using. |
Closing this due to lack of input. |
I'm running an app running off the base sdk iOS 8 and I'm running into a problem with my code:
When I init with my center controller as my app delegate's rootviewcontroller, I get the following error in iOS 8:
adding a root view controller <UITabBarController: 0x11425fc0> as a child of view
Is there a workaround for this?
The text was updated successfully, but these errors were encountered: