-
Notifications
You must be signed in to change notification settings - Fork 58
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
Handle notification params replacement being null #1203
Conversation
Signed-off-by: Thomas Citharel <tcit@tcit.fr>
Integration tests failure don't seem to be related? |
Can you try to catch the case to get the details which notification is a problem? |
The activity in question that generates the notification seems to be the following:
The notification is sent to User 2. User 1 has shared the calendar with user 2, and updated an event in that calendar. The notification itself is properly displayed. Am I understanding this correctly in thinking this is because |
In the database acotr as string is fine. |
Can you confirm that the calendar name and object name are real strings (and not null) and displayname of the user 1 is set to a non-empty string? I still don't get how a null could get in there. |
Two issues I stumbled over:
But nothing that would bring in a null which then throws... Also I would tend to just go with a check to use the ID if name is null/empty string to help more with debugging, instead of having untranslated parameters afterwards in the strings. |
That's the issue, user 1's displayname is indeed |
Which use backend are you using? The Displayname normally falls back to the uid |
Regular database backend, running on 23.0.4. |
I can't see how this happens either, following the flow seems to work as expected. I'll try to reproduce with the actual activity data to make sure. |
Is the user id null as well? Otherwise I can not see how this could happen |
It's not. Maybe it's something else. |
Closing for now |
Unclear how & why this happens, but at least now it's handled.