-
Notifications
You must be signed in to change notification settings - Fork 94
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
Notification was not parsed by any notifier [app: text, subject: mentioned] #5884
Comments
Thanks for the report @SystemKeeper. This is a info level log message and it comes from https://github.com/nextcloud/server/blob/e5a6698ec0125d0183b3e71d27e4d22dae0431bc/lib/private/Notification/Manager.php#L357 Not sure either where this could come from, also given that mentioning in a document works and results in notifications in my tests. |
I also could not trigger a debugger breakpoint when sending a notification for a mention. @SystemKeeper Can you maybe share the related entry that was created in your oc_notifications table? |
I was thinking about this morning. Could it be that - during an update - the app was temporarily disabled while at the same some one tried to fetch the notifications? I'll try to verify that with the access logs |
That is the only notification of the user in question.
So seems not related to the update. But I don't see anything weird in this entry? I also checked that |
Is |
I replaced it. It has the same format as "marcel.mueller", and also does not contain any special characters. |
Is from last october. So is a very old notification. |
Describe the bug
Not really sure if it is a bug, but I noticed this in the log of an instance.
From the error I would assume it happens when someone was mentioned in a text document. But when I manually try it, it works. So not sure what triggers the exception.
Screenshots
If applicable, add screenshots to help explain your problem.
Server details:
Logs
Nextcloud log (data/nextcloud.log)
The text was updated successfully, but these errors were encountered: