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
I would like assistance with the following scenario:
How to reproduce:
Create two users: A and B.
Login with user A's credentials on one Android device.
Login with user B's credentials on two different Android devices.
Start sending notifications from user A to user B.
Both of user B's devices are receiving notifications, but I want only the latest logged-in device to receive notifications. The goal is to have only the most recent device logged in to receive notifications, while older devices do not.
Question: If a user logs in on multiple devices, for example, logging in first on a Samsung Android phone and then on a Google Pixel phone, notifications are currently being sent to both devices. However, I want only the most recently logged-in device to receive notifications.
Is there a way to either delete the old session data without user interaction or implement another solution to ensure only the latest logged-in device receives the notification?
The text was updated successfully, but these errors were encountered:
Hello,
I would like assistance with the following scenario:
How to reproduce:
Both of user B's devices are receiving notifications, but I want only the latest logged-in device to receive notifications. The goal is to have only the most recent device logged in to receive notifications, while older devices do not.
Question: If a user logs in on multiple devices, for example, logging in first on a Samsung Android phone and then on a Google Pixel phone, notifications are currently being sent to both devices. However, I want only the most recently logged-in device to receive notifications.
Is there a way to either delete the old session data without user interaction or implement another solution to ensure only the latest logged-in device receives the notification?
The text was updated successfully, but these errors were encountered: