Tarun_Sharma reports an issue with the notification API where only the first reaction to a post appears in /notifications.json, and subsequent reactions from other accounts do not update the merged notification until one of them is removed. Tarun_Sharma further explains the issue by describing the behavior when reacting with multiple accounts. Moin asks about the recipient’s notification preferences, but Tarun_Sharma clarifies that this is not related to preferences and suggests it’s a notification merging/refresh bug. tobiaseigen believes this behavior is by design, explaining that notifications are not updated for subsequent reactions but are updated when a reaction is retracted.
https://{defaultHost}/notifications.json
When a single user reacts to a post with emojis, the correct notification is generated. However, if multiple users react to the same post, the updated notification with the correct reaction count only appears when one of the users removes their reaction.
How can we fix this issue?
Is there any solution for this.
I reacted on a post from account A I get notificaton data in notification api for that notification then when I reacted on same post with Account B I dont’t get it data in notification api.But when I remove my reaction from Account A then Account B notification data is coming in notification api.Then I again react on post with Account A notification data come in api then I remove notification from Account B then Account A notification data is coming.
How did the user whose posts you reacted to configure their like notification preferences? Is that configured to notify on every like?
I don’t think this is related to the recipient’s notification preferences. The user whose post I reacted to has the default setting (Notify when liked: “First time and daily”), not “Every time”. But even with that, the issue isn’t about whether they get notified — it’s that in /notifications.json only the very first reaction shows up, and subsequent reactions from other accounts don’t update the merged notification until one of them is removed.
So it looks more like a notification merging/refresh bug rather than a preference setting.
I think the behavior you are describing is by design. If you like or react to a post, the person who wrote the post gets a notification. If others then like or add reactions, the notification is not updated. It makes sense to me that the notification is updated if someone retracts their like or reaction.