Skip to content
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

feature request: permanent notification #374

Open
iddq opened this issue Sep 11, 2024 · 3 comments
Open

feature request: permanent notification #374

iddq opened this issue Sep 11, 2024 · 3 comments
Labels
a:feature New feature or request request-for-comments

Comments

@iddq
Copy link

iddq commented Sep 11, 2024

Please make the .setOngoing property of the notification remotely accessible.

@jmattheis
Copy link
Member

Describe your use-case. The android docs specify that "the application or service must take care of canceling them". How do you envision this? https://developer.android.com/reference/android/app/Notification.Builder#setOngoing(boolean)

@jmattheis jmattheis added the question Further information is requested label Sep 13, 2024
@iddq
Copy link
Author

iddq commented Sep 13, 2024

When creating the notification, we would provide the ID, which we could later use in a cancel request and thus revoke the previously created notification, regardless of whether it is permanent or not. Controllability of setAutoCancel would also be useful.

The permanent notification is advantageous because the user cannot delete it. Revoking a notification remotely can also be useful in certain situations. Sorry if your program already knows this, but I haven't noticed it yet.

@jmattheis
Copy link
Member

Hmm, I don't think many users need this, let's wait for some feedback from other users.

@jmattheis jmattheis added request-for-comments a:feature New feature or request and removed question Further information is requested labels Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:feature New feature or request request-for-comments
Development

No branches or pull requests

2 participants