Skip to content
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

Unbalanced calls to begin/end appearance transitions #196

Open
MartinMoizard opened this issue Jan 3, 2014 · 6 comments
Open

Unbalanced calls to begin/end appearance transitions #196

MartinMoizard opened this issue Jan 3, 2014 · 6 comments
Labels

Comments

@MartinMoizard
Copy link

After a setCenterViewController:withCloseAnimation:Completion: I get the following message: "Unbalanced calls to begin/end appearance transitions for <UINavigationViewController: 0xbd73670>."

Here are the steps to reproduce:

  • Call [self setCenterViewController:controllerA withFullCloseAnimation:YES completion:nil];
  • Call [self toggleDrawserSide:MMDrawerSideLeft animated:YES completion:nil];
  • Call again [self setCenterViewControllersetCenterViewController:controllerA withFullCloseAnimation:YES completion:nil];

=> The message gets printed and the app starts to behave strangely.

Any idea of to fix that?

Thanks

@MartinMoizard
Copy link
Author

Here is the workaround I'm using for now:

[self setCenterViewController:controllerA];
[self toggleDrawerSide:MMDrawerSideLeft animated:YES completion:nil];

@nottix
Copy link

nottix commented Jan 9, 2014

+1

@knightmj
Copy link

I am also seeing this problem.

@ObjectiveB
Copy link

Same here. But using the FullCloseAnimation option results in an ugly animation exposing the cut-off left drawer (width < device width).

@kcharwood
Copy link
Contributor

I think I may have isolated this problem. I tracked down an issue where if you set the center view controller to the same center view controller while trying to close it, you would get the unbalanced log. Fix coming soon.

@kcharwood
Copy link
Contributor

Just submitted a pull request (#219) and released version 0.5.3. Let me know if that fixes it for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants