Unbalanced calls to begin end appearance transitions for UITabBarController 0x197870

Question

I read SO about another user encountering similar error  but this error is in different case   I received this message when I added a View Controller initially   Unbalanced calls to begin end appearance transitions for   lt UITabBarController  0x197870 gt    The structure of the app is as follow   I got a 5-tab TabBarController linked to 5 View Controllers  In the initial showing tab  I call out a new View Controller to overlay as an introduction of the app   I use this code to call the introduction view controller   IntroVC  vc     IntroVC alloc  init    self presentModalViewController vc animated YES    vc release      After this IntroVC view controller shows up  the above error shows    p s  I am using xCode 4 2  amp  iOS 5 0 SDK  developing iOS 4 3 app

User · Answer

If you re using transitioningDelegate  not the case in this question s example   also set modalPresentationStyle to  Custom   Swift  let vc   storyboard instantiateViewControllerWithIdentifier        vc transitioningDelegate   self vc modalPresentationStyle    Custom

User · Answer

I had the same error  I have a tab bar with 3 items and I was unconsciously trying to call the root view controller of item 1 in the item 2 of my tab bar using performSegueWithIdentifier   What happens is that it calls the view controller and goes back to the root view controller of item 2 after a few seconds and logs that error   Apparently  you cannot call the root view controller of an item to another item    So instead of performSegueWithIdentifier   I used  self parentViewController tabBarController setSelectedIndex 0    Hope this helps someone

User · Answer

I had the same issue  When developing I wanted to bypass screens  I was navigating from one view controller to another in viewDidLoad by calling a selector method    The issue is that we should let the ViewController finish transitioning before transitioning to another ViewController      This solved my problem  The delay is necessary to allow ViewControllers finish transitioning before transitioning to another    self perform  selector YOUR SELECTOR METHOD   with  self  afterDelay  0 5

User · Answer

As posted by danh  You can generate this warning by presenting the modal vc before the app is done initializing  i e  Start a tabbed application template app and present a modal vc on top of self tabBarController as the last line in application didFinishLaunching  Warning appears  Solution  let the stack unwind first  present the modal vc in another method  invoked with a performSelector withDelay 0 0  Try to move the method into the viewWillAppear and guard it so it does get executed just once  would recommend setting up a property

User · Answer

Swift 5   func scene   scene  UIScene  willConnectTo session  UISceneSession  options connectionOptions  UIScene ConnectionOptions        Delete or comment the below lines on your SceneDelegate             guard let windowScene    scene as  UIWindowScene  else   return             window  windowScene   windowScene           window  makeKeyAndVisible            let viewController   ListVC           let navViewController   UINavigationController rootViewController  viewController          window  rootViewController   navViewController

User · Answer

I had the same problem and thought I would post in case someone else runs into something similar   In my case  I had attached a long press gesture recognizer to my UITableViewController   UILongPressGestureRecognizer  longPressGesture      UILongPressGestureRecognizer alloc                                                     initWithTarget self                                                    action  selector onLongPress                                                      autorelease    longPressGesture setMinimumPressDuration 1    self tableView addGestureRecognizer longPressGesture     In my onLongPress selector  I launched my next view controller   -  IBAction onLongPress  id sender        SomeViewController  page     SomeViewController alloc  initWithNibName   SomeViewController  bundle nil         self navigationController pushViewController page animated YES         page release        In my case  I received the error message because the long press recognizer fired more than one time and as a result  my  SomeViewController  was pushed onto the stack multiple times    The solution was to add a boolean to indicate when the SomeViewController had been pushed onto the stack   When my UITableViewController s viewWillAppear method was called  I set the boolean back to NO

User · Answer

I fixed this error by changing animated from YES to NO   From    tabBarController presentModalViewController viewController animated YES     To    tabBarController presentModalViewController viewController animated NO

User · Answer

As  danh suggested  my issue was that I was presenting the modal vc before the UITabBarController was ready  However  I felt uncomfortable relying on a fixed delay before presenting the view controller  from my testing  I needed to use a 0 05-0 1s delay in performSelector withDelay    My solution is to add a block that gets called on UITabBarController s viewDidAppear  method   PRTabBarController h    interface PRTabBarController   UITabBarController   property  nonatomic  copy  void   viewDidAppearBlock  BOOL animated     end   PRTabBarController m    import  PRTabBarController h    implementation PRTabBarController  -  void viewDidAppear  BOOL animated        super viewDidAppear animated       if  self viewDidAppearBlock            self viewDidAppearBlock animated             end   Now in application didFinishLaunchingWithOptions   PRTabBarController  tabBarController     PRTabBarController alloc  init       UIWindow initialization  etc     weak typeof tabBarController  weakTabBarController   tabBarController  tabBarController viewDidAppearBlock     BOOL animated        MyViewController  viewController    MyViewController new       viewController modalPresentationStyle   UIModalPresentationOverFullScreen      UINavigationController  navigationController     UINavigationController alloc  initWithRootViewController viewController        weakTabBarController tabBarController presentViewController navigationController animated NO completion nil       weakTabBarController viewDidAppearBlock   nil

User · Answer

I had this problem when I had navigated from root TVC to TVC A then to TVC B  After tapping the  load  button in TVC B I wanted to jump straight back to the root TVC  no need to revisit TVC A so why do it   I had     Pop child from the nav controller  self navigationController popViewControllerAnimated YES     Pop self to return to root  self navigationController popViewControllerAnimated YES        which gave the error  Unbalanced calls to begin end etc   The following fixed the error  but no animation     Pop child from the nav controller  self navigationController popViewControllerAnimated NO     Then pop self to return to root  self navigationController popViewControllerAnimated NO     This was my final solution  no error and still animated     Pop child from the nav controller  self navigationController popViewControllerAnimated NO     Then pop self to return to root  only works if first pop above is  not  animated  self navigationController popViewControllerAnimated YES

User · Answer

I had this problem with a third party code  Someone forgot to set the super inside of viewWillAppear and viewWillDisappear in a custom TabBarController class   -  void  viewWillAppear  BOOL animated         super viewWillAppear animated          code       or  -  void  viewWillDisappear  BOOL animated         super viewWillDisappear animated          code

User · Answer

Actually you need to wait till the push animation ends  So you can delegate UINavigationController and prevent pushing till the animation ends   -  void navigationController  UINavigationController   navigationController didShowViewController  UIViewController   viewController animated  BOOL animated      waitNavigation   NO      - void showGScreen  id gvc       if   waitNavigation            waitNavigation   YES            nav popToRootViewControllerAnimated NO             nav pushViewController gvc animated YES

User · Answer

I solved it by writing   self navigationController presentViewController viewController                                          animated TRUE                                        completion NULL

User · Answer

In Swift 2  for me works   I have UITabBarViewController in storyboard and I had selectedIndex property like this     But I delete it  and add in my viewDidLoad method of my initial class  like this   override func viewDidLoad        super viewDidLoad      self tabBarController  selectedIndex   2     I hope I can help someone

User · Answer

Another solution for many cases is to make sure that the transition between UIViewControllers happens after the not-suitable  like during initialization  procedure finishes  by doing     weak MyViewController  weakSelf   self  dispatch async dispatch get main queue            weakSelf presentViewController vc animated YES         This is general for also pushViewController animated   etc

User · Answer

you need make sure - void beginAppearanceTransition  BOOL isAppearing animated  BOOL animated and - void endAppearanceTransition is create together in the class

User · Answer

I found that  if you are using a storyboard  you will want to put the code that is presenting the new view controller in viewDidAppear  It will also get rid of the  Presenting view controllers on detached view controllers is discouraged  warning

User · Answer

I had the same problem when I need to Present My Login View Controller from another View Controller If the the User is t authorized  I did it in ViewDidLoad Method of my Another View Controller   if not authorized -  presentModalViewController    When I start to make it in ViewDidAppear method  I solved this problem  I Think that ViewDidLoad only initialize properties and after that the actual showing view algorithm begins  Thats why you must use viewDidAppear method to make modal transitions

User · Answer

I had the same problem  I called a method inside viewDidLoad inside my first UIViewController  -  void viewDidLoad       super viewDidLoad         self performSelector  selector loadingView                 withObject nil afterDelay 0 5      -  void loadingView        self performSegueWithIdentifier   loadedData  sender self       Inside the second UIViewController I did the same also with 0 5 seconds delay  After changing the delay to a higher value  it worked fine  It s like the segue can t be performed too fast after another segue

User · Answer

For me this error occurred because i didn t have UIWindow declared in the upper level of my class when setting a root view controller             rootViewController  showTimeoutAlert   showTimeOut             let navigationController   SwipeNavigationController rootViewController  rootViewController               self window   UIWindow frame  UIScreen main bounds              self window  rootViewController   navigationController             self window  makeKeyAndVisible    Ex if I tried declaring window in that block of code instead of referencing self then I would receive the error

User · Answer

I had this problem because of a typo   override func viewDidAppear animated  Bool        super viewWillAppear animated    instead of   override func viewDidAppear animated  Bool        super viewDidAppear animated    It was calling  WillAppear  in the super instead of  DidAppear

User · Answer

I encountered this error when I hooked a UIButton to a storyboard segue action  in IB  but later decided to have the button programatically call performSegueWithIdentifier forgetting to remove the first one from IB   In essence it performed the segue call twice  gave this error and actually pushed my view twice   The fix was to remove one of the segue calls   Hope this helps someone as tired as me

User · Answer

Without seeing more of the surrounding code I can t give a definite answer  but I have two theories    You re not using UIViewController s designated initializer initWithNibName bundle   Try using it instead of just init  Also  self may be one of the tab bar controller s view controllers  Always present view controllers from the topmost view controller  which means in this case ask the tab bar controller to present the overlay view controller on behalf of the view controller  You can still keep any callback delegates to the real view controller  but you must have the tab bar controller present and dismiss

User · Answer

I had lot of problem with the same issue  I solved this one by   Initiating the ViewController using the storyboad instantiateViewControllerWithIdentifier method  i e Intro  vc    self storyboard instantiateViewControllerWithIdentifier   introVC     self tabBarController presentModalViewController   vc animated YES     I have the viewcontroller in my storyboard  for some reason using only   introvc alloc  init   did not work for me

[ios] Unbalanced calls to begin/end appearance transitions for <UITabBarController: 0x197870>

Examples related to ios

Examples related to ios4

Examples related to uitabbarcontroller