The current implementation of isLauncherInitialized allows TAPL tests to run while LoaderTask is still binding items. This can lead to interactions on a launcher that is not yet drawn/responsive.
Flag: N/A
Fixes: 313043156
Test: TaplAppIconMenuTest#testLaunchMenuItem
Change-Id: I4cb9276eb3852653517faa45be8517e659f39c00
> Simplifying some try-catch stamtements
> Removing unnecessary interface implementation
> Using kotlin native null check, which also prevents NullpointExeception
when using calling methods from a non-main thread
Bug: 314010650
Flag: N/A
Test: Presubmit
Change-Id: I435ace5df8d7a19a8bba4099408f6cc7257d1f1f
AccessibilityManager.registerSystemAction is a binder call that should be run on the ui helper thread. It is only used for the taskbar and likely ran slowly ON THE UI thread, causing an ANR.
Flag: N/A
Fixes: 313923168
Test: ran launcher
Change-Id: Icf8d7282df5bffd4aae2f4ec94f997b555c3b8c1
This is a no-op thoroughly tested by ReorderAlgorithmUnitTest.
Flag: NA
Bug: 229292911
Test: ReorderAlgorithmUnitTest
Change-Id: I9909477274aadbbf928c9fdeb4157d697c4c7175
Bug: 311613831
Flag: NONE
Test: Manual, i.e. testing predictive back to home and analysing taskbar animation
Change-Id: I87d9ba065a43ee99ff1c7b35478b2828a482bd7b
enableSplitFromFullscreenWithKeyboardShortcuts() depends on enableSplitContextually() from the product perspective, hence merging these two flags
Bug: 270394122
Test: N/A
Change-Id: Iecf46a62bfa21ed0c3bad9ca8c9e2646b3aebc78
This controls whether a haptic is played when search invocation
starts. The assumption is that the search app will play this
haptic if the flag is disabled (default).
Test: Manual
Bug: 310659178
Bug: 314005577
Flag: LEGACY ENABLE_SEARCH_HAPTIC_COMMIT DISABLED
Change-Id: I406c18cfaf27d004e19de26f00c997c0a03de996
This will help to ensure that Launcher state has settled before continuing the test.
Bug: 313926097
Flag: N/A
Test: presubmit
Change-Id: I8bed0225617a225c2dc9587a75d004b98395fe1f
This way we can still log long press attempts even when the
feature flags or settings are disabled.
We always log LAUNCHER_LONG_PRESS_NAVBAR when a long press is
detected, even if nothing else happens.
Additionally, we log LAUNCHER_DEEP_PRESS_NAVBAR if the long
press was short-circuited by a deep press. In this case both
logs will appear.
If ENABLE_LPNH_DEEP_PRESS is false, it's possible that
LAUNCHER_DEEP_PRESS_NAVBAR will be logged without
LAUNCHER_LONG_PRESS_NAVBAR. This is because we log deep press
even if the feature is disabled, but it won't cause long press to
trigger immediately, so the user may release their finger before
the normal long press triggers.
Note: getLongPressRunnable will still return null if the flags or
other checks fail, so nothing will happen beyond logging.
Fix: 313477667
Fix: 310955078
Test: Manual with wwlogcat with flags in various states
Flag: NA
Change-Id: I40ceb5a22b364c2d5d6e4fdabb546b81c84354eb
Sebastián Franco
Schneider Victor-tulias
Stefan Andonian
Holly Sun
Andy Wickham
Saumya Prakash
Federico Baron
Vinit Nayak
Sunny Goyal
Jagrut Desai
Vadim Tryshev
Tracy Zhou
Bill Yi
Johannes Gallmann
Jordan Silva
Andreas Agvard
Thales Lima
Pat Manning
Anna Zhuravleva
Winson Chung
Jon @
Brandon Dayauon