Fixed
Status Update
Comments
ia...@gmail.com <ia...@gmail.com> #2
Is there any way to use this while it's not available, without a big if else where we do everything duplicated? Like this example.
val notification = if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.S) {
Notification.Builder(...)
.setContentTitle("Title")
.setStyle(...)
// Duplicate everything here!!!
.build()
} else {
NotificationCompat.Builder(...)
.setContentTitle("Title")
.setStyle(...)
// Duplicate everything here!!!
.build()
}
il...@google.com <il...@google.com>
il...@google.com <il...@google.com>
il...@google.com <il...@google.com>
mg...@google.com <mg...@google.com>
ap...@google.com <ap...@google.com> #3
Hi,
Could you at least tell us if you will add the CallStyle to the NotificationCompat API?
Best regards,
ap...@google.com <ap...@google.com> #4
Yes. Our goal is to provide an implementation that uses CallStyle on API 31+ and uses the new fields to produce a usable call notification, based on the device's standard template, on older versions of Android.
pr...@google.com <pr...@google.com> #5
Thanks for the answer. Do you have an estimated ETA?
Description
Component used:
androidx.lifecycle:lifecycle-viewmodel-ktx
Version used:
2.5.1
Devices/Android versions reproduced on: n/a
Given the new APIs for adding closables to view models,
viewModelScope
should probably be marked as discouraged or deprecated in order to promote testability.