You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Previously, when multiple similar notifications are scheduled, only one of them gets accepted and the app server throws a NotificationAlreadyExistsException for the rest of them. The check for this is below:
Thus when multiple notifications of the same title, body, and timestamp are scheduled, only one of them is sent. However, this might have worked previously because the type property was incorrectly set when sent from the Questionnaire app. However, when the type is set correctly (the type is set as the questionnaire name), even when the notification has the same title, body, and timestamp, but the questionnaire name is unique, this still gets scheduled.
Priority
A value between 1-10 signifying the Priority that you think this bug should be dealt with. 1 denotes highest priority.
6
Difficulty
A value between 1-10 signifying the amount of difficulty/work/time that you think will be involved in fixing this bug. 10 denotes highest difficulty
3
To Reproduce
Schedule multiple questionnaires to be valid at the same time (e.g. all PHQ8, RSES questionnaires at 9am everyday).
Expected behavior
Only one of the same type of notification should be shown (same title, body, and timestamp).
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
I would have thought that is a required feature - i.e to have multiple notifications for different questionnaires? But i see the point that if the title and body is same, then does it add any value?
I think this is related to the previous conversation about grouping similar notifications into one notification -- RADAR-base/RADAR-Questionnaire#1448
I would have thought that is a required feature - i.e to have multiple notifications for different questionnaires? But i see the point that if the title and body is same, then does it add any value?
I think this is related to the previous conversation about grouping similar notifications into one notification -- RADAR-base/RADAR-Questionnaire#1448
Ah okay I see. Okay yes we can have a separate implementation of this through the protocol as discussed here: RADAR-base/RADAR-Questionnaire#1448.
Describe the bug
Previously, when multiple similar notifications are scheduled, only one of them gets accepted and the app server throws a
NotificationAlreadyExistsException
for the rest of them. The check for this is below:RADAR-Appserver/src/main/java/org/radarbase/appserver/service/FcmNotificationService.java
Lines 167 to 175 in c8c0439
Thus when multiple notifications of the same title, body, and timestamp are scheduled, only one of them is sent. However, this might have worked previously because the
type
property was incorrectly set when sent from the Questionnaire app. However, when thetype
is set correctly (the type is set as the questionnaire name), even when the notification has the same title, body, and timestamp, but the questionnaire name is unique, this still gets scheduled.Priority
A value between 1-10 signifying the Priority that you think this bug should be dealt with. 1 denotes highest priority.
6
Difficulty
A value between 1-10 signifying the amount of difficulty/work/time that you think will be involved in fixing this bug. 10 denotes highest difficulty
3
To Reproduce
Schedule multiple questionnaires to be valid at the same time (e.g. all PHQ8, RSES questionnaires at 9am everyday).
Expected behavior
Only one of the same type of notification should be shown (same title, body, and timestamp).
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: