It seems that the new implementation of the Firebase Cloud Messaging API v1 is not handling invalid tokens. According to Firebase documentation, if response is UNREGISTERED (error 404), then it means that token is invalid.
For the legacy API there was a handling implemented in SAP Marketing by checking tokens before sending messages and marking as "invalid" those that Google ID API identified as such.
Now it seems that it does not care and is not making changes to tokens based on a response of the new API v1.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.