[Feature request] Send notification in different channel in case of error #1053
Milestone
Comments
mendhak
added a commit
that referenced
this issue
May 26, 2024
…rmissions or unable to write file. Issue #1053 Issue #1158
mendhak
added a commit
that referenced
this issue
May 26, 2024
… service to only after the permission check is complete. In the stop service, only stop the service if notifications are enabled, due to a weird scenario where the service might start and immediately end due to lack of notifications, resulting in an app crash. How did we end up like this. Issue #1138 Issue #1053
|
I've done some work on this yesterday. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If a session is in progress but logging fails for some reason, the app should send a notification to let the user know.
I generally leave the app running 24/7 and have hidden the constant notification from the device's notification settings. Several times now the logging has failed and I only noticed several days later because I happened to open the app.
The logging has failed for several reasons, for example when logging to a local file and storage fills up or permissions get changed. Basically any time red warning text gets printed to log view.
It might be useful to have notifications for warnings too (timeout reached, etc) but they should be in a separate channel from errors.
The text was updated successfully, but these errors were encountered: