-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
feat: better offline operations notification handling #15451
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: better offline operations notification handling #15451
Conversation
| setLargeIcon(BitmapFactory.decodeResource(context.resources, R.drawable.notification_icon)) | ||
| setStyle(NotificationCompat.BigTextStyle()) | ||
| priority = NotificationCompat.PRIORITY_LOW | ||
| setChannelId(NotificationUtils.NOTIFICATION_CHANNEL_DOWNLOAD) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This line was overriding the NOTIFICATION_CHANNEL_BACKGROUND_OPERATIONS thus it needs to be removed.
…ion action Signed-off-by: alperozturk <alper_ozturk@proton.me>
Signed-off-by: alperozturk <alper_ozturk@proton.me>
373a91f to
1c47a34
Compare
|
APK file: https://www.kaminsky.me/nc-dev/android-artifacts/15451.apk |
|
/backport to stable-3.33 |

Issue
Multiple offline operations can fail, and users may receive notifications for each failure. If a user attempts to execute the same operation again, the notification may reappear (e.g. #15420 (comment)). In the worker, certain offline operations are canceled and removed from the database. For example, when an operation completes successfully, or if it is a rename or delete operation. In the case of rename or delete operations, conflicts may occur; to prevent overwriting the server’s latest changes, the worker only informs the user instead of executing the action automatically.
Changes
This PR introduces a new notification action for failed offline operations, allowing users to manually remove them if they do not wish to retry.
Additionally, the offline operations worker now uses a dedicated notification channel, giving users the option to manage or disable these notifications independently.
Note: Adding a more descriptive label for the cancel action, such as "Cancel Offline Operation," could make the notification appear cluttered, as the title already conveys the purpose of the notification.