tree 26da3570a7656bcf19eddd1d61e98ba60728cf74
parent 2e0eee4d63df82a1df460aa2c05a1482565a435f
author Tony Wickham <twickham@google.com> 1617736022 -0700
committer Tony Wickham <twickham@google.com> 1617736560 -0700

Consolidate two different onTransitionCancelled implementations

There was previously two different onTransitionCancelled(), one in
BaseActivityInterface and one in AnimationFactory. They are pretty
similar and the differences seem subtle and not necessary. In this
bug, the AnimationFactory version was going to mStartState instead
of StateManager#getRestState() (which is the same, unless mStartState
disables restore). Instead, always use the mActivityInterface
implemenation, which seems more robust.

Test: Open app A, open app B, quick switch from B to A, swipe home
during that transition, then touch nav region during home transtion;
ensure we don't goToState(BACKGROUND_APP) in the subsequent
onTransitionCanceled().

Fixes: 184583037

Change-Id: I315a5087b12413d88c3ccc1e3245a55a76a73e62