You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which package manager are you using? (Yarn is recommended)
npm
If the issue is web-related, please select the bundler (web.bundler in the app.json)
metro
Summary
Hi, Im new on react native and i'm trying to implement google oath without firebase on an expo app. I set up all the credentials good in the google console following the doc.
I'm getting this error
expoClientId is not supported anymore and should have been removed. You cannot use Google auth-session in Expo Go anymore. Create a dev client to get unblocked here. This will use the bundle identifier as the redirect_uri which should match the bundle id you added to the Google cloud console.
…uth proxy. (#28590)
# Why
- Related #28544
- expoClientId would be used when running in Expo Go to use a web
authentication in a native app. This only worked with the auth proxy
which we deprecated a while ago.
---------
Co-authored-by: Expo Bot <34669131+expo-bot@users.noreply.github.com>
Minimal reproducible example
https://github.com/testmyyapp/Sign-In-With-Google-TEST
Which package manager are you using? (Yarn is recommended)
npm
If the issue is web-related, please select the bundler (
web.bundler
in theapp.json
)metro
Summary
Hi, Im new on react native and i'm trying to implement google oath without firebase on an expo app. I set up all the credentials good in the google console following the doc.
I'm getting this error
I tried everything, i m stuck.
Environment
expo-env-info 1.2.0 environment info:
System:
OS: Linux 6.5 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)
Shell: 5.1.16 - /bin/bash
npmPackages:
@expo/webpack-config: ^19.0.1 => 19.0.1
expo: ^49.0.23 => 49.0.23
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: 0.72.10 => 0.72.10
react-native-web: ~0.19.6 => 0.19.10
Expo Workflow: managed
The text was updated successfully, but these errors were encountered: