goBack() doesn't work well with pending transactions.

[lassem]

The old version of the library used move to go back in history, while as 1.0 alpha uses a synchronous call to setHistory.

This doesn't work well in our case and I'm suggesting it is wrong behavior.

What happens in our case:

1. Key 1 is on the backstack
2. Key 1 pushes Key 2, Key 3 and Key 4 to the backstack, traversal begins.
3. Key 4 decides that the work it was supposed to do was not needed. Calls goBack
   • Calling goBack from here does not work as expected as Key 2, Key 3 and Key4 are not yet in the history.
4. After the call to goBack from Key 4 we're at Key 1; not Key 3 as expected.

[Zhuinden]

Key 4 decides that the work it was supposed to do was not needed.

Traversals are not cancelable. It says so on the interface declaration.

So if setHistory(}K1,K2,K3,K4}) is called, then callback.onTraversalComplete() finishes, then goBack() will go to K1,K2,K3 which means the top is K3.

[lassem]

Okay. I'm closing this then.

The current workaround is to do a Handler.post()