onNewToken() returns the wrong token

[night556]

onNewToken() returns the wrong token

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[lehcar09]

Hi @night556, thank you for reaching out. I tried reproducing the issue, however, I did not encounter an issue with the token I received in my app. I was able to send a message successfully in the app using Admin SDK - Node.js and Firebase console. I'ts possible that the VPN is what's causing the issue. Have you tried disabling your VPN?

[night556]

Thank you for your reply, for some reason we need to use a VPN to get the token. we can't get more information about the situation without a VPN, but we will be adding logs to record the situation later, I will reply here if there is more information.
Lastly, I would like to know if in this case it can be assumed with a high probability that it is due to the VPN that is causing the issue.

[night556]

If it's due to a VPN, what's the root cause usually?

[lehcar09]

Hi @night556, based on our documentation,

VPNs mask the underlying information that FCM needs to tune its connection to maximize reliability & battery life. In some cases VPNs actively break long lived connections resulting in a bad user experience due to missed or delayed messages or a high battery cost...Different VPNs will have different methods for controlling whether or not it can be bypassed. Consult the documentation for your specific VPN for instructions.

I suggest reaching out to the Firebase support channel instead. We'd need access to your project settings (including projectID, SHA-1 etc) to troubleshoot this type of issue.

[night556]

Thanks for the advice.