I am a developer and have some games on Google Play. Recently, I received an email that said one of my games has used the OAuth Loopback IP address flow (Having redirect URI on the call, more information in this link (https://developers.google.com/identity/protocols/oauth2/resources/loopback-migration). I have implemented the Google Play Games Service in the game since 2019 and it is using the given client id in the email.
I am not sure whether the problem was caused by this package or not. Since after Android 7.0 that is not easy to view the HTTPS request, I have tried using Charles and Wireshark but still cannot show the request header.
I am a developer and have some games on Google Play. Recently, I received an email that said one of my games has used the OAuth Loopback IP address flow (Having redirect URI on the call, more information in this link (https://developers.google.com/identity/protocols/oauth2/resources/loopback-migration). I have implemented the Google Play Games Service in the game since 2019 and it is using the given client id in the email.
I am not sure whether the problem was caused by this package or not. Since after Android 7.0 that is not easy to view the HTTPS request, I have tried using Charles and Wireshark but still cannot show the request header.