So… there seems to have been some significant change in the Google Sign In in Expo 32… a lot of the original config settings have been deprecated apparently…
There is a lot more information here regarding your general frustration rather than the issue itself. What happens when the authentication doesn’t work? Is a modal shown, is an error thrown?
GoogleSignIn was made in accordance to a change that Google made which prevented any kind of sandboxing native authentication.
The android client IDs did nothing in the prior releases, and the web client ID was the server ID. Removing these is more of a clarification rather than a feature.
Can you confirm that you have configured your project in accordance to the setup guide in the docs. Google Sign-In Setup
Consider that there is no way to set the client ID during runtime on Android, meaning there is no JS property that you can set. You need to define the relative path to your google-services.json in the app.json as specified in step 6. On the API side your project also needs to have authentication enabled.
On Android everything API related is automatic. Meaning it is not related to a bug in the Expo API layer. You will also need to ensure that GoogleSignIn.getPlayServiceAvailability() returns true as well.
the issue is directly related to the URI redirect. Could you please share that value (with the API key obfuscated if you’d like (even though it’s a public value)). I’m suspecting that in standalone you may need to use the reverse client ID instead of a package ID. But hard to determine.
Hello! I have been stuck on this problem too. I am trying to test the google sign in feature with Expo client on an Android Emulator. I have a WEB type client id. My code looks like this:
Your answer relates to bare/stand-alone apps and not us using the Expo.Google in the expo client right? Do I have to eject my expo client app in order to use your new GoogleSignIn module? If that’s the case why does it say it’s pre-installed in managed expo projects? Sorry for many questions but this is confusing.
My Google Sign in is broken since upgrading to SDK 32 on both standalone builds and development. I get an error on Google.logInAsync() and even when I try AppAuth.authAsync()