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
Is your feature request related to a problem? Please describe.
Currently we accumulate FCM tokens indefinitely which leads to significant unnecessary overhead when notifications are sent.
Describe the solution you'd like
We should remove tokens that are no longer valid to reduce the clutter. It looks like we may receive a specific error message from Firebase when we attempt to send to an invalid token:
http error status: 404; reason: app instance has been unregistered; code: registration-token-not-registered; details: Requested entity was not found.
There may be other cases in which we want to remove these tokens as well but we will need to be careful not to remove them based on errors that are due to a temporary state.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently we accumulate FCM tokens indefinitely which leads to significant unnecessary overhead when notifications are sent.
Describe the solution you'd like
We should remove tokens that are no longer valid to reduce the clutter. It looks like we may receive a specific error message from Firebase when we attempt to send to an invalid token:
There may be other cases in which we want to remove these tokens as well but we will need to be careful not to remove them based on errors that are due to a temporary state.
The text was updated successfully, but these errors were encountered: