So I have a datatype, Messages, with a user field (assigned to user), and with a field status (Option Set values: New, Clicked, Hidden). I have a notification bell that will show the number of New messages, and once those messages are clicked or hidden, they change the status of that message according to the action taken.
The number on the notification bell is a text field populated by the dynamic value Search for Messages (with constraint of status = new, user = current user): count. This text also has a conditional to display only when that same search:count is >= 1.
This works fine - as long as you are one tab. However, if I have multiple tabs open, the behavior is not as predictable. On PC, it seems to work fine, as I click on one message, the notification count updates on both open tabs.
However, I noticed on my Android, it doesn’t update when the message is clicked on the desktop, but the desktop does update when the message is clicked on the Android mobile. So even though there are no new messages, the Android notification count will remain at the previous number (2 for example).
This is not a typical use case for me or my customers (as there wouldn’t be a reason to use my app on more than one tab), but it is something I notice as I’m testing things on my app with multiple browsers and devices.
I went a step further and rather than change the value of the status field through user actions, I just changed them via the backend through the database. When I change a message from hidden to new, the notification count predictable increases across all tabs, both in PC and android mobile. However, if I change the status from New to Hidden, the Android does not update the counter (which should return to 0 and thus not display), while the PC does update as it should.
Furthermore, if I change the same message status from hidden to new and new to hidden, the Android (using chrome FYI), does not increase the count, and will only increase the count when a new message is assigned a status of new.
So there seems to be an issue with a “ghost” result that is being stuck in the mobile, that is only removed when the change is made on that devices browser, whereas the PC results will update regardless of where the change was made.
Again, not a real issue for me, but I’m curious as to what is causing this behavior and if there is a better way to design the logic to avoid this.