How to detect and delete stale/invalid device tokens
What are the best practices when it comes to remove stale device tokens from the device token list
SIs this related to FCM?
S@Poison
Pyes I use fcm tokens for both android and ios
STwo of the best practices, I've read about are:
- having an inactivity threshold, and
- having an automatic clean up process
SDo you want any resources on this?
Pyes that would be great!
Sgive me a few mins
SPcool, but I assume this wont remove the stale tokens from the novu user?
Sno, I thought you wanted to remove from FCM
S1 minute
SI think this same method can be used to update the credentials of a subscriber. You can pass an array with new tokens to update the subscriber and the old ones should be replaced with the new ones I believe.
Try logging the response and confirming it
Try logging the response and confirming it
Pyeah I think i'll need to have a similar cron job to go to each token and check if it's expired and delete it
N@Poison, you just advanced to level 1!
PThanks
Ssure, anytime!
MI came in to ask the same question. This does not appear to be true, I always add via and the returned subscriber object contains all tokens ever added.
SInteresting, let me get back to you!
P@Mal Curtis and @Poison
Update subscriber credentials api and setCredentials method in nodejs sdk appends a new token in array.
We have unique check in place to store only unique tokens.
To remove one/multiple tokens from subscriber credentials check out how to remove token docs section.
Let me know if you face any issue
Update subscriber credentials api and setCredentials method in nodejs sdk appends a new token in array.
We have unique check in place to store only unique tokens.
To remove one/multiple tokens from subscriber credentials check out how to remove token docs section.
Let me know if you face any issue
MThanks @Pawan Jain . The issue I see is that sometimes the device token in a browser is a new token, but we have no record of what token that browser originally used. So we can either a. delete all tokens - thus removing tokens from devices that should be receiving notifications, or b. leave invalid tokens on the user which just fail on every push notification. Is there a third method I can't see here? Perhaps storing a device token in local storage so we can check if it has changed? I'm not sure how reliable this would be.