Status Update
No update yet.
Comments
ap...@google.com
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()
}
ap...@google.com
Hi,
Could you at least tell us if you will add the CallStyle to the NotificationCompat API?
Best regards,
ap...@google.com
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.
ap...@google.com
Thanks for the answer. Do you have an estimated ETA?
ap...@google.com
Any update on this please?
se...@google.com
Could you please give us an ETA?
na...@google.com
Hello again,
It's been a while now that Android 12 has been released, and it would be great to have an estimated time of arrival for this feature in appcompat package so we can plan our developments & releases as app developers.
Thanks in advance.
Description
Version used: 2.8.1
Devices/Android versions reproduced on: Android 10, 13
Our app uses both JobScheduler (in older part) and WorkManager (in newer code)
We noticed that jobs and workers never start on Android 11 and 13 devices connected to a private network (no internet access).
Older devices (Android 8) work fine.
It seems to be related to JobInfo.setRequiredNetworkType creating a NetworkRequest with NET_CAPABILITY_INTERNET and NET_CAPABILITY_VALIDATED.
On the JobScheduler side we fixed the problem by specifying the required network with a proper NetworkRequest instead of a networkType.
Unfortunately this is not possible with the WorkManager.
I believe that private networks are quite common in enterprise environment. The WorkManager is currently not suitable for this use case.
More generally it would be nice to be able define the required network more precisely.
In our case, the workaround we can think of are :
- Modify the URL used to validate the network (via OEM config), so that the devices believe they have internet access. It work but it's ugly and only possible for some devices.
- Migrate the code from WorkManager to JobScheduler. Interestingly enough we were previously considering the opposite.