Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FCM Token Lifecycle #211

Open
kiritowu opened this issue Feb 4, 2025 · 0 comments
Open

FCM Token Lifecycle #211

kiritowu opened this issue Feb 4, 2025 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@kiritowu
Copy link
Collaborator

kiritowu commented Feb 4, 2025

As user login to the portal, a Firebase Cloud Messaging token is requested from server/local cache.

The backend needs to store the token in database as it is needed to sent notification for user.

One user can have multiple FCM token given that they might be logged in on different devices or sessions. Additionally, FCM token may be staled as user logged out or not active after 30 days.

Appropriate logic is required to manage FCM token lifecycle to improve the delivery rate of notifications.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant