I propose a Notification Troubleshooting page, kind of like what Element Android and Element X Android have.
It would run some tests, notably:
Whether the user has granted Fluffy the permission to send notifications
Displaying a notification (without push, from the foreground activity)
Detecting available Push Providers
(as set by the user see #1133)
Trying to use the currently set provider
performing a check to see whether the provider is online
checking the notification token, e.g Firebase token
Trying to send a push
Rationale
It is really hard to debug notification issues on FluffyChat. You have to figure out what backend Fluffy is trying to use, whether it can send notifications over it, and lots of other workarounds until you either find the root of your problem or find an alternative to your preferred notifications system.
Mockup
I had no time to make a mockup myself, but this page from Element X could serve as inspiration:
Additional Context
This issue and issue is largely there to facilitate discussion about this feature.
Feature Description
I propose a Notification Troubleshooting page, kind of like what Element Android and Element X Android have.
It would run some tests, notably:
Rationale
It is really hard to debug notification issues on FluffyChat. You have to figure out what backend Fluffy is trying to use, whether it can send notifications over it, and lots of other workarounds until you either find the root of your problem or find an alternative to your preferred notifications system.
Mockup
I had no time to make a mockup myself, but this page from Element X could serve as inspiration:
Additional Context
This issue and issue is largely there to facilitate discussion about this feature.