| commit | 2f52c713149f950fdd689d1f688e4cc17e7e42d6 | [log] [tgz] |
|---|---|---|
| author | Selim Cinek <cinek@google.com> | Fri Jul 19 11:47:58 2019 -0700 |
| committer | android-build-team Robot <android-build-team-robot@google.com> | Tue Jul 23 03:37:13 2019 +0000 |
| tree | 654588f31f116697ffc7f76991682c871d8b0961 | |
| parent | e86a1924306ac46c7d22c4eff691467efee23c4b [diff] |
Fixed a crash with the headsUpManager Since the headsUpManager is calling out in various places to its listeners, the callbacks may query the headsupmanager in an internally inconsistent state, such that the pinned mode is true but there is no topEntry. Let's add a null-check for safety here. Bug: 137804505 Test: atest SystemUITests Change-Id: Ibae76b555ca51ccf676228b034a614d59a8b4e8e (cherry picked from commit 41e7e6edc74e27235f6057def04dd9a6e18f3a8a)