Android Push Notification : http v1 not_found 404 : unregistered error after updating to API http v1

Hi ,
I have a question regarding the update from HTTP Legacy to HTTP v1 for Android push notification configuration. After making the update, we noticed a significant increase in invalid user errors during the send-out process. Has anyone else experienced this issue? If so, were you able to identify the cause? Could it be related to ACC's inability to determine the validity of many tokens over the past few months, resulting in a buildup of invalid tokens that we are only seeing now?

Thank You.