From 8ad32a5a37bfcfeb00e3eccbbccb2549f6bd8e75 Mon Sep 17 00:00:00 2001
From: Nataniel Borges <natanieljr@google.com>
Date: Fri, 3 Mar 2023 21:52:16 +0000
Subject: [PATCH] Fix splashscreen layer identification

Bug: 271553459
Test: atest FlickerTests
Change-Id: Iadea7dcbe216af493c74fb769c460632e29d516e
---
 .../server/wm/flicker/launch/OverrideTaskTransitionTest.kt     | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/tests/FlickerTests/src/com/android/server/wm/flicker/launch/OverrideTaskTransitionTest.kt b/tests/FlickerTests/src/com/android/server/wm/flicker/launch/OverrideTaskTransitionTest.kt
index da985232a1e32..b848e63c9c87d 100644
--- a/tests/FlickerTests/src/com/android/server/wm/flicker/launch/OverrideTaskTransitionTest.kt
+++ b/tests/FlickerTests/src/com/android/server/wm/flicker/launch/OverrideTaskTransitionTest.kt
@@ -93,8 +93,7 @@ class OverrideTaskTransitionTest(val flicker: FlickerTest) {
                 .then()
                 // Animation starts, but the app may not be drawn yet which means the Splash
                 // may be visible.
-                .isInvisible(testApp, isOptional = true)
-                .isVisible(ComponentNameMatcher.SPLASH_SCREEN, isOptional = true)
+                .isSplashScreenVisibleFor(testApp, isOptional = true)
                 .then()
                 // App shows up with the custom animation starting at alpha=1.
                 .isVisible(testApp)