Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 1b895828 authored by Josh Tsuji's avatar Josh Tsuji
Browse files

Revert "Revert "Always start dismiss transition when the going a..."

Revert submission 27773289-revert-27770576-DGMSFQBZGQ

Reason for revert: Test failure was unrelated

Reverted changes: /q/submissionid:27773289-revert-27770576-DGMSFQBZGQ

Change-Id: Ifb4e5c22dbed97728ec4a64d88237bc280a89dee
parent 7c7f8bd3
Loading
Loading
Loading
Loading
+10 −8
Original line number Diff line number Diff line
@@ -142,15 +142,17 @@ constructor(
        nonApps: Array<RemoteAnimationTarget>,
        finishedCallback: IRemoteAnimationFinishedCallback
    ) {
        if (apps.isNotEmpty()) {
        // Ensure that we've started a dismiss keyguard transition. WindowManager can start the
            // going away animation on its own, if an activity launches and then requests dismissing
            // the keyguard. In this case, this is the first and only signal we'll receive to start
            // a transition to GONE.
        // going away animation on its own, if an activity launches and then requests dismissing the
        // keyguard. In this case, this is the first and only signal we'll receive to start
        // a transition to GONE. This transition needs to start even if we're not provided an app
        // animation target - it's possible the app is destroyed on creation, etc. but we'll still
        // be unlocking.
        keyguardTransitionInteractor.startDismissKeyguardTransition(
            reason = "Going away remote animation started"
        )

        if (apps.isNotEmpty()) {
            goingAwayRemoteAnimationFinishedCallback = finishedCallback
            keyguardSurfaceBehindAnimator.applyParamsToSurface(apps[0])
        } else {