Status Update
Comments
su...@google.com <su...@google.com> #2
Can someone please provide an example of Notification.BigPictureStyle().bigPicture(...)
working with an animated image? From the description of this issue and the API 31 requirement, I am assuming an Icon must be passed to .bigPicture()
. However, what configurations does the Icon need in order to animate?
I have scoured the internet, but am unable to find a single example of this even though Google boldly announced it in
Edit: Also requested
ro...@gmail.com <ro...@gmail.com> #3
Branch: androidx-main
commit a2b7f7b7268c8f24b6e3a66bf58017f39c329b68
Author: Alexander Roederer <aroederer@google.com>
Date: Thu Jun 16 17:45:43 2022
Adds support for BigPictureStyle using Icon
Modifies Notification.java to use Icon as the base representation
for BigPicture in BigPictureStyle. Also adds tests to ensure both
Icon and Bitmap representation are functional.
Bug: 215583339
Test: NotificationCompatTest integration tests added
Relnote: Adds support for BigPictureStyle using Icon
Change-Id: Ice26d1400836cdf74af931f0f8ca59c25dd9c3c3
M core/core/api/restricted_current.txt
M core/core/src/main/java/androidx/core/app/NotificationCompat.java
M core/core/api/public_plus_experimental_current.txt
M core/core/src/androidTest/java/androidx/core/app/NotificationCompatTest.java
M core/core/api/current.txt
su...@google.com <su...@google.com> #4
Flag flipped in
Description
Version used:1.0.0-alpha02
Devices/Android versions reproduced on: all
Hi,
maybe I'm missing something in the documentation.
My intention was to create a periodic work that should run once a day (each 24 hours). I did two mistakes: I forgot to give the job a tag, and I forgot to check if the job was already in the queue before enqueueing it.
As result of error n2, each time that a user opens the app, a new job is enqueued. Only one job should be fired a day per user, but in my backend logs I can see that this happens multiple times per user.
As result of the error n1, I can not cancel those jobs (because they do not have a tag). I suppose the only solution is to uninstall the app and install it again.
Maybe it would be a nice feature to have a method to cancel all scheduled works, with or without tags. Or a method to get all current works, without tags, an then cancel them by Id.
Or at least to make the tag for a job mandatory, to be able to cancel the task in the future.
Another question that I did not find answer for is: what happens to current scheduled works, if the tag name is changed? Are the new one enqueued, and the old ones remains alive or what?
Thank and apologizes about my English.