NotificationCompat.Builder setChronometerCountdown throws NullPointerException [145770610]

Fixed

Bug

[AOSP] assigned

Status Update

No update yet.

Description

al...@gmail.com

created issue #1

Dec 6, 2019 02:34PM

Artifact used 'androidx.core:core-ktx:1.2.0-rc01'

- Relevant code to trigger the issue.
val builder= NotificationCompat.Builder(context, SNOOZING_CHANNEL_ID)
builder.setUsesChronometer(true)
builder.setChronometerCountDown(true) throws NPE

workaround:
call builder.addExtras(Bundle()) before builder.setChronometerCountDown(true)

Origin:

https://android.googlesource.com/platform/frameworks/support/+/androidx-master-dev/core/core/src/main/java/androidx/core/app/NotificationCompat.java#839

This bug is linked to:

https://issuetracker.google.com/issues/37132891 and

https://issuetracker.google.com/issues/138601213 that can be closed now imho.

Comments

vi...@google.com <vi...@google.com> Dec 9, 2019 06:48AM

Assigned to vi...@google.com.

vi...@google.com <vi...@google.com> #2Dec 9, 2019 10:53AM

Reassigned to ki...@google.com.

Hi, thanks for reaching out to us and reporting this issue! Will share this to the internal teams and open a report on your behalf. Will reach back with updates as soon as I have one.

Thanks!

ki...@google.com <ki...@google.com> Dec 9, 2019 02:07PM

Reassigned to ob...@google.com.

ap...@google.com <ap...@google.com> #3Apr 8, 2020 03:16AM

This has created significant limitations in our app - we need to enable COEP so we can use SharedArrayBuffer for some performance-intensive code, however we currently can't do this and embed YouTube videos at the same time, which we need to support. Credentialless/anonymous iframes would theoretically also solve this issue, but this is not widely adopted in browsers (and WebKit is in fact resistant to implementing it due to user safety concerns:

https://github.com/WebKit/standards-positions/issues/45)

ob...@google.com <ob...@google.com> Apr 8, 2020 03:17AM

Marked as fixed.

Issue 145770610