Summary: | Sometimes notifications are the wrong type | ||
---|---|---|---|
Product: | [Applications] Tokodon | Reporter: | Joshua Goins <josh> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | carl, josh |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/network/tokodon/-/commit/4b115bcf2e366fa494a060e0e929eec1a5af10e5 | Version Fixed In: | 24.12.1 |
Sentry Crash Report: |
Description
Joshua Goins
2024-12-26 16:57:54 UTC
Git commit 4b115bcf2e366fa494a060e0e929eec1a5af10e5 by Joshua Goins. Committed on 26/12/2024 at 20:38. Pushed by redstrate into branch 'master'. Fix crash when receiving unknown notifications There's a Q_UNREACHABLE() in the default case, but this turns out to be pretty bad. The server can send unknown notifications behind our back or we don't send it post it as a notification yet. This fixes a regular crash I've seen when receiving push notifications. I also added a warning I can grep for in the logs whenever a notification type is unknown. M +4 -2 src/account/notificationhandler.cpp M +7 -1 src/timeline/notification.cpp M +2 -1 src/timeline/notification.h M +5 -0 src/tokodon.notifyrc https://invent.kde.org/network/tokodon/-/commit/4b115bcf2e366fa494a060e0e929eec1a5af10e5 |