diff options
| author | 2024-07-30 00:53:35 +0000 | |
|---|---|---|
| committer | 2024-07-30 00:53:35 +0000 | |
| commit | 5cf0be2d2fb19b9e6d1e2085670dfa2010f5efaf (patch) | |
| tree | 798b8e8985263c2059af1bacdc00e152e42d403d /libs/androidfw/StringPool.cpp | |
| parent | c2f344e80fe37e89291c8032298119a45dd723c2 (diff) | |
Avoid harmless NPE in sendResultReceiverFailureLocked()
This is a follow up CL to my previous CL [1], which removed
ZeroJankProxy.Callback#isInputShownLocked().
While I apparently overlooked scenarios when ResultReceiver is null,
we catch the NPE then only print the stacktrace to logcat [2], which
is why we could not notice it in presubmit.
Let's fix it to avoid confusions. There must be no user-observable
behavior change anyway.
[1]: Ib719f6018965c3554c8c2d8c2050ad51962d8a25
a5ebd6b7812136ab2d98f0ac0b8fa6aed2862193
[2]: I008198157424c544d4973eb94434b458e27f15fd
34730c43845b1ab629e7e1250c207c43b92d935a
Bug: 349904272
Test: presubmit
Flag: android.view.inputmethod.use_zero_jank_proxy
Change-Id: Idf898fb4ca7fdef64e81d92a124f035d244ff3b3
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions