From 2e8bc06a77b1a289d98a4a8707b1c01bfcd78ffc Mon Sep 17 00:00:00 2001
From: Nataniel Borges <natanieljr@google.com>
Date: Tue, 4 Jul 2023 16:28:35 +0000
Subject: [PATCH] Wait until PIP has the correct bounds before continuing

Bug: 288353930
Test: atest WMShellFlickerTestPip
Change-Id: I92ec51ea2a5e7e396ff4c618e03c6530f3257d1b
---
 .../src/com/android/server/wm/flicker/helpers/PipAppHelper.kt  | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/tests/FlickerTests/src/com/android/server/wm/flicker/helpers/PipAppHelper.kt b/tests/FlickerTests/src/com/android/server/wm/flicker/helpers/PipAppHelper.kt
index 24e231c73a0f4..c975a50ace020 100644
--- a/tests/FlickerTests/src/com/android/server/wm/flicker/helpers/PipAppHelper.kt
+++ b/tests/FlickerTests/src/com/android/server/wm/flicker/helpers/PipAppHelper.kt
@@ -250,10 +250,13 @@ open class PipAppHelper(instrumentation: Instrumentation) :
             waitConditions = arrayOf(ConditionsFactory.hasPipWindow())
         )
 
+        val windowRegion = wmHelper.getWindowRegion(this)
+
         wmHelper
             .StateSyncBuilder()
             .withWindowSurfaceAppeared(this)
             .withPipShown()
+            .withSurfaceVisibleRegion(this, windowRegion)
             .waitForAndVerify()
     }