You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I updated my project to Swift 4 to support iOS 11 in my application and im experiencing a strange behaviour when pushing and popping view controllers created programmatically. (In my project I don't use Storyboards or Nibs, so all my view controllers are created programmatically)
When I push a view controller created programmatically onto the SlideNavigationController's stack, the transition animation looks strange. The same thing happens when it is popped from the stack.
I have another pod, a loader (CCActivityHUD), that works fine until I push a programmatically created view controller for the first time. After that, it stops showing on any screen.
I tried using a view controller created via Storyboard and using the method 'instantiateViewControllerWithIdentifier' to access it, and the visual bug disappears!
Has anybody experienced a similar behaviour?
The text was updated successfully, but these errors were encountered:
I updated my project to Swift 4 to support iOS 11 in my application and im experiencing a strange behaviour when pushing and popping view controllers created programmatically. (In my project I don't use Storyboards or Nibs, so all my view controllers are created programmatically)
When I push a view controller created programmatically onto the SlideNavigationController's stack, the transition animation looks strange. The same thing happens when it is popped from the stack.
I have another pod, a loader (CCActivityHUD), that works fine until I push a programmatically created view controller for the first time. After that, it stops showing on any screen.
I tried using a view controller created via Storyboard and using the method 'instantiateViewControllerWithIdentifier' to access it, and the visual bug disappears!
Has anybody experienced a similar behaviour?
The text was updated successfully, but these errors were encountered: