We have an Activity that contains a SlidingMenu (https://github.com/jfeinstein10/SlidingMenu) in which there's three options, let's call them A, B1, C1. These correspond to Fragments that we show in the Activity. When you select a different option from the SlidingMenu I replace the current fragment with the new one via the FragmentManager.
From Fragment B1 you can go to two others, let's call them B2 and B3. Here we want the Back key to take you from B2 -> B1 or from B3 -> B1, so I call transaction.addToBackStack(null). If we select an option from the SlidingMenu when you're on B2 or B3 we want to clear the back stack, so I use code as suggested in this question Clear back stack using fragments which calls popBackStack() until it's clear.
So far so good.
From Fragment C1 you can go to Fragment C2. As C1/C2 are more of a Master/Detail design I use
fragmentTransaction.setCustomAnimations(R.animator.slide_in_from_right,
R.animator.slide_out_to_left, R.animator.slide_in_from_left,
R.animator.slide_out_to_right);
to add a slide animation where C1 slides out to the left as C2 slides in from the right, and vice versa. Pressing the Back key while on C2 takes us back to C1, with the reverse animation, and all is good.
BUT
If you select A or B1 from the SlidingMenu and we popBackStack() to get rid of C1 from the back stack, then it slides C2 out to the right, which looks weird. What I'd like to do is clear the back stack without running the animation, but I can't find a way to do that. I've tried calling popBackStackImmediate() instead, but that doesn't seem to make any difference.
As an alternative I guess I could avoid calling addToBackStack at all, and instead manually handle the user pressing the Back key via Activity.onBackPressed(), but perhaps there's a solution I just can't see?