-
Notifications
You must be signed in to change notification settings - Fork 56
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
trigger "notification:test-push" via mobile apps (to self test push notifications) #1206
Comments
Current issue is that all notification handling is user based and using a real notification. |
sure. all we need would be a new type for the notification, like "selfcheck"? |
As far as I can tell this feature is currently not possible to implement, because the OCP IManager does not expose a way to send a notification to a single token and not to the all the devices a user has, right? |
Since we are the app that handles pushing, we can add an endpoint to do exactly that ourselves. |
It should be possible to trigger
sudo -u www-data php /var/www/yourinstance/occ notification:test-push --talk youruser
via API, so the mobile apps could have a "Test Notifications" button in the settings-view.
That notification should be catched on mobile clients and they show a success dialog.
If notification is not received within x seconds, show a dialog with the link to the troubleshooting checklist etc.
With this every user could check that pushproxy is working or not and it can be narrowed down why a notifications is not shown..
If possible, also give feedback to the mobile clients that the "notification:test-push" command was successfully executed on server...
The text was updated successfully, but these errors were encountered: