AppCompatTextView.setCustomSelectionActionModeCallback with null callback causes crash on Oreo [173435375]

Fixed

Bug

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Nov 17, 2020 04:28AM

Component used: AppCompat Version used: appcompat-1.2.0 Devices/Android versions reproduced on: Oreo, API level 26 & 27

To reproduce:

Create AppCompatTextView and invoke setCustomSelectionActionModeCallback(null).
Long click on its text to bring up the selection action menu.
Observe crash.

This arises from the fact that AppCompatTextView.setCustomActionModeCallback accepts nullables, but internally calls to TextViewCompat.wrapCustomSelectionActionModeCallback, which requires a non-null callback.

Offending lines:

https://cs.android.com/androidx/platform/frameworks/support/+/androidx-master-dev:appcompat/appcompat/src/main/java/androidx/appcompat/widget/AppCompatTextView.java;l=446

https://cs.android.com/androidx/platform/frameworks/support/+/androidx-master-dev:core/core/src/main/java/androidx/core/widget/TextViewCompat.java;l=516

To fix this, the OreoCallback wrapping should be skipped if the callback is null.

Comments

ki...@google.com <ki...@google.com> Nov 17, 2020 02:54PM

Reassigned to al...@google.com.

te...@google.com <te...@google.com> #2Jan 22, 2021 07:24PM

So what is the recommendation on where to observe LiveData? onViewCreated? Because at one point, the docs were using onActivityCreated.

al...@google.com <al...@google.com> Feb 17, 2021 09:01PM

Accepted by al...@google.com.

ap...@google.com <ap...@google.com> #3Apr 16, 2021 04:02PM

Marked as fixed.

Re #2 - They're called back to back, so they'd be equally valid (for a Fragment with a View).

Issue 173435375

Description

Issue summary

Comments

ki...@google.com <ki...@google.com> Nov 17, 2020 02:54PM

te...@google.com <te...@google.com> #2Jan 22, 2021 07:24PM

al...@google.com <al...@google.com> Feb 17, 2021 09:01PM

ap...@google.com <ap...@google.com> #3Apr 16, 2021 04:02PM

Add comment

Issue metadata