fix: Invalid push notification tokens are not cleaned up from database for FCM API v2 #9173
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request
Issue
Closes: #9085
Approach
The references on how to manage the token responses:
Tokens will be cleaned up in the following cases:
messaging/registration-token-not-registered
messaging/invalid-registration-token
messaging/invalid-argument
but only if error message isThe registration token is not a valid FCM registration token
--> I tested this out; this error response is received if the token format itself is invalid, for example a token value ofinvalid_test_token
Tasks