René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Handle invalid token responses in FCM","articleBody":"As per the [documentation](https://firebase.google.com/docs/cloud-messaging/manage-tokens#ensuring-registration-token-freshness) a token could be invalid if you have two error codes:\n\n- UNREGISTERED (HTTP 404)\n- INVALID_ARGUMENT (HTTP 400) \n\nHowever INVALID_ARGUMENTS can be caused by other errors.\n\nAt the moment we receive the content below from the `IncomingHttpResponse` which is also the error message from the `FirebaseMessagingException`. What we do is to check the string of the message in order to delete these tokens.\n\n\n```\nContent: {\n  \"error\": {\n    \"code\": 400,\n    \"message\": \"The registration token is not a valid FCM registration token\",\n    \"status\": \"INVALID_ARGUMENT\",\n    \"details\": [\n      {\n        \"@type\": \"type.googleapis.com/google.firebase.fcm.v1.FcmError\",\n        \"errorCode\": \"INVALID_ARGUMENT\"\n      }\n    ]\n  }\n}\n```\n\n\nWhat is the proper way to handle these errors?\nDoes it make sense to update FirebaseMessagingException to provide more information about which field is invalid or perhaps have a new error code - INVALID_TOKEN? This would remove a lot of unambiguity as to when it is needed to manage the token.","author":{"url":"https://github.com/yanikapitanov","@type":"Person","name":"yanikapitanov"},"datePublished":"2025-01-24T12:16:06.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/1064/firebase-admin-java/issues/1064"}