Google-signin: Getting 'Developer_Error' after changing project credentials to a newer one

Created on 17 Oct 2020  路  3Comments  路  Source: react-native-google-signin/google-signin

I have managed to get the package to work just fine. Important to mention that I followed the instructions for non-firebase users. With the previous credentials (client_id) it was working fine, but as soon as I deleted the old project and created a new one with new credentials on google developers console I was getting developer_error although I have changed the server_client_id value inside strings.xml and provided the configure method with the right parameters.

So if anyone has faced a similar situation, would be great if you share your solution.

Most helpful comment

Yes I am facing same issue in android device when using google signin shows developer_error_aacount.
Using webClientID

All 3 comments

Yes I am facing same issue in android device when using google signin shows developer_error_aacount.
Using webClientID

Yes I am facing same issue in android device when using google signin shows developer_error_aacount.
Using webClientID

This helped me a lot 馃馃徎

for those having same problem, if you changed the project file google-services.json file you should run ./gradlew clean before running the app again. that worked for me.

Was this page helpful?
0 / 5 - 0 ratings