Had it running perfectly in the Emulator, however I had to make some further modifications to get it to work in a production build on an actual device: 1. Upon sign-in I got a stacktrace with the error "DEVELOPER_ERROR:10". Turns out I had to use the SHA-1 from the "Setup > App signing > SHA-1" in the Google Play Console. 2. In Supabase I had to put my Web Client Credentials (Client ID & Secret) into the Google Provider. I also added the same Web Client ID into the Authorized Client IDs field. Hope this helps.
hey, how about native google sign in on Apple applications, it returns mismatch as it seems there is no place to add iOS client ID under google provider
Documentation on Sign in with google page says that sign in with google is outdated and no longer supported, how can we use the android credential manager to login in instead?
Hola, todos los que hablan españo, tuve un pequeño impedimento, en el cual salia el error de ERROR_DEVELOPMEN, en lo cual se soluciono creando otra api key y generando nuevamente el hash key y funcionó
Public Version: Available on the public npm registry, this version does not include One-tap sign-in (it uses the deprecated Google Sign-In for Android), Web and macOS support found in the sponsor-only version. ------ Why would I use it then?
I got this error towards the end of the video when i added utils/supabase. The app worked fine be4 trying to load supabase. Note: don't think it was in the video but I installed react-native-url-polyfill with "npx expo install react-native-url-polyfill;" Any idea? ERROR Error: URL.hostname is not implemented, js engine: hermes ERROR Invariant Violation: "main" has not been registered.
error in the chapter implement sign in button ERROR RN GoogleSignin native module is not correctly linked. Please read the readme, setup and troubleshooting instructions carefully or try manual linking. ERROR TypeError: Cannot read property 'SIGN_IN_CANCELLED' of null, js engine: hermes
I followed every step until 16:40, the Google pop-up shows and when I connect with google I have a [Error: DEVELOPER_ERROR]. I checked my SHA 1, my package name, ma AndroidManifest, my string.xml, the set up un my Google Console... Can someone give me some advice to debug that ? :) thanks !
Hello great video, but im having this problem: RN GoogleSignin native module is not correctly linked. Please read the readme, setup and troubleshooting instructions carefully or try manual linking. Do you have any advice?
hi, the problem you have is a bout you cant run google-sign-in library on expo go, if you see the app.json you find the path "googleServicesFile": "./android/app/google-services.json", you will never be able to connect that in expo go, the explanation is long ,instead of that run npx expo run:android.
this is correct, you actually don't need to touch any native code when using the expo config plugin, so you can ignore the part here ruclips.net/video/vojHmGUGUGc/видео.htmlsi=C3h9whxrB21Vxo-s&t=368 This is because RNGS already adds that dependency, so no need to do it again. (I'm the maintainer of RN google sign in)
I was about to ask if instead of touching the native code, if this tutorial can be done completely in Expo (fully managed workflow) pretend using a 'Development Build' instead of prebuilding and touching the generated android code. I saw your comment and was wondering if you got this working purely with JS/TypeScript expo code? If so, how would the steps in this tutorial change?
@@armyofda12monkeys you do need to prebuild. But after that, there's no touching of the native code. It cannot be done purely with JS code, so google sign in won't work in Expo Go
The legacy auth method is also unsupported now, so I'm not sure how to get this working without paying the maintainer of the library they use for the updated version. Did you find a different way to implement this?
This is for the "Original Google sign in" right? Seems the maintainer has now split it so there's a "One-tap Google sign in" version for sponsors only. Just want to see which version this is for
Just ignore the One-tap Google sign in and do the original way. That way will work just fine, no need to pay for the premium version of the Google sign in for react library
Thanks! Works perfectly localy, but after i build an apk file and install it on real device. "Sign in" button stops working with no errors. Just nothing happens when i try to tap it
Hello. I am at 16:17 and the google popup opens, I am able to select a google account but when I press "next" it says "Something went wrong" and if I press the "next" button again I get redirect to a browser with 400 error saying "The server cannot process the request because it is malformed. It should not be retried" did you encounter this error? or what could be the isse? thank you!
Bro, i have this problem, any idea?? ERROR Invariant Violation: "main" has not been registered. This can happen if: * Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project. * A module failed to load due to an error and `AppRegistry.registerComponent` wasn't called., js engine: hermes
Had same issue yesterday. What did it for me is delete .expo, node-modules, android, ios folders from root of project. Then do npx expo prebuild --clean and npx react-native start --reset-cache Also I had an issue with upgrading to expo SDK 51 from 49: in the package.json your "main" should actually point to your entry point, can't use the expo-router/entry as before. Next thing is that at the end of your entry point file you should always have the registerRootComponent(App); where App is your entry point component name. Hope this helps!
Had it running perfectly in the Emulator, however I had to make some further modifications to get it to work in a production build on an actual device:
1. Upon sign-in I got a stacktrace with the error "DEVELOPER_ERROR:10". Turns out I had to use the SHA-1 from the "Setup > App signing > SHA-1" in the Google Play Console.
2. In Supabase I had to put my Web Client Credentials (Client ID & Secret) into the Google Provider. I also added the same Web Client ID into the Authorized Client IDs field.
Hope this helps.
why did the google sign in process become so complex??
Its shocking how awful Google is with creating and publishing apps. The difficulty level of doing the most basic things is incredible
Please make a continuation video where the authenticated user is interacting with the supabase database ie creating something like posts
Here it is :) ruclips.net/video/AE7dKIKMJy4/видео.html
This is the only tutorial I've found that is clear and actually works. Thank you so much!
hey, how about native google sign in on Apple applications, it returns mismatch as it seems there is no place to add iOS client ID under google provider
Documentation on Sign in with google page says that sign in with google is outdated and no longer supported, how can we use the android credential manager to login in instead?
Great video, met supabase for this video and really love supabase now!
Great you sponsor it ❤
Warning: Google Sign-In for Android is outdated and no longer supported. google now forcing to use credential manager
Yes RNGooglesign is not working with expo
Is there a tutorial or guide on how to implement it using credential manager? if there is then can you provide a link to the guide?
@@sutharjay1 so how to do that
am I the only one stucket with an error 400 from google? "this app doesn't comply with google's Oauth2"
Hola, todos los que hablan españo, tuve un pequeño impedimento, en el cual salia el error de ERROR_DEVELOPMEN, en lo cual se soluciono creando otra api key y generando nuevamente el hash key y funcionó
Public Version:
Available on the public npm registry, this version does not include One-tap sign-in (it uses the deprecated Google Sign-In for Android), Web and macOS support found in the sponsor-only version.
------
Why would I use it then?
Hello, does this work with Expo managed apps? Or only with bare ones ?
Thanks your video is so helpful
I got this error towards the end of the video when i added utils/supabase. The app worked fine be4 trying to load supabase.
Note: don't think it was in the video but I installed react-native-url-polyfill with "npx expo install react-native-url-polyfill;"
Any idea?
ERROR Error: URL.hostname is not implemented, js engine: hermes
ERROR Invariant Violation: "main" has not been registered.
nvm, i manually uninstalled the app from the emulator. and re-ran the 'npx expo run:android'. I think it worked after that.
error in the chapter implement sign in button ERROR RN GoogleSignin native module is not correctly linked. Please read the readme, setup and troubleshooting instructions carefully or try manual linking.
ERROR TypeError: Cannot read property 'SIGN_IN_CANCELLED' of null, js engine: hermes
for these kind of sht I stopped using react native. Everything involves a cascade of "before doing this..."
Thank you so much, this tutorial was very helpful!
Finally, you guys have been so focused on flutter that you've missed the more popular alternative.
thank you for the amzing tutorial
I followed every step until 16:40, the Google pop-up shows and when I connect with google I have a [Error: DEVELOPER_ERROR].
I checked my SHA 1, my package name, ma AndroidManifest, my string.xml, the set up un my Google Console...
Can someone give me some advice to debug that ? :)
thanks !
i also get error like you, then i can't slove it. Is anyone can help me ? :)
Hello great video, but im having this problem: RN GoogleSignin native module is not correctly linked. Please read the readme, setup and troubleshooting instructions carefully or try manual linking. Do you have any advice?
hi, the problem you have is a bout you cant run google-sign-in library on expo go, if you see the app.json you find the path "googleServicesFile": "./android/app/google-services.json", you will never be able to connect that in expo go, the explanation is long ,instead of that run npx expo run:android.
question. You are setting the expo config plugin. There is no need to touch the native code when building with expo eas
this is correct, you actually don't need to touch any native code when using the expo config plugin, so you can ignore the part here ruclips.net/video/vojHmGUGUGc/видео.htmlsi=C3h9whxrB21Vxo-s&t=368
This is because RNGS already adds that dependency, so no need to do it again.
(I'm the maintainer of RN google sign in)
You are correct, thanks for pointing that out! Will see to update the README and the video.
I was about to ask if instead of touching the native code, if this tutorial can be done completely in Expo (fully managed workflow) pretend using a 'Development Build' instead of prebuilding and touching the generated android code. I saw your comment and was wondering if you got this working purely with JS/TypeScript expo code? If so, how would the steps in this tutorial change?
@@armyofda12monkeys you do need to prebuild. But after that, there's no touching of the native code. It cannot be done purely with JS code, so google sign in won't work in Expo Go
what is the problem with IOS? Could you explain how to work with IOS?
i recommend read the docs
If I follow these steps, will it work on my iOS app as well?
probably not
Why are there so many different processes for this? just need a working solution that hasn't been deprecated yet
Isn't the library using the legacy auth method for this flow though?
The legacy auth method is also unsupported now, so I'm not sure how to get this working without paying the maintainer of the library they use for the updated version. Did you find a different way to implement this?
why the self hosted version different from platform version and also make the same as platform for self hosted
I urgently need the Flutter version :)
Coming right up!
Same lol
@@J3R3MI6 I found the solution but it would still be good for other friends to have a video
Hi supabase, do you have tutorial on how to combine supabase and react query?
This is a good one by a community member: makerkit.dev/blog/saas/supabase-react-query
This is for the "Original Google sign in" right? Seems the maintainer has now split it so there's a "One-tap Google sign in" version for sponsors only. Just want to see which version this is for
Just ignore the One-tap Google sign in and do the original way. That way will work just fine, no need to pay for the premium version of the Google sign in for react library
Thanks! Works perfectly localy, but after i build an apk file and install it on real device. "Sign in" button stops working with no errors. Just nothing happens when i try to tap it
Hi！ may I ask how you ultimately completed this task? I have been working on it recently，I'd appreciate some help
Super useful video!😀
Error: DEVELOPER_ERROR i dont know wt to do now
Did you find a solution?
this is now outdated :( please can you upload a new video
You can integrate with web based auth without relying on react native google sign in. that's the way we are doing it in production
You can integrate with web based auth without relying on react native google sign in. that's the way we are doing it in production.
Qual a opção mais atualizada para isso? Você tem alguma alternativa?
can we do google passkey authentication with expo?
Hello. I am at 16:17 and the google popup opens, I am able to select a google account but when I press "next" it says "Something went wrong" and if I press the "next" button again I get redirect to a browser with 400 error saying "The server cannot process the request because it is malformed. It should not be retried" did you encounter this error? or what could be the isse? thank you!
I was using my mobile device connected via USB Debugging. this was the issue!
and in js?
Bro, i have this problem, any idea??
ERROR Invariant Violation: "main" has not been registered. This can happen if:
* Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project.
* A module failed to load due to an error and `AppRegistry.registerComponent` wasn't called., js engine: hermes
Had same issue yesterday. What did it for me is delete .expo, node-modules, android, ios folders from root of project. Then do npx expo prebuild --clean and npx react-native start --reset-cache
Also I had an issue with upgrading to expo SDK 51 from 49: in the package.json your "main" should actually point to your entry point, can't use the expo-router/entry as before. Next thing is that at the end of your entry point file you should always have the registerRootComponent(App); where App is your entry point component name. Hope this helps!
How did you fixed this issue?
@@emanuilnikolov8662 can you please share the code if you Have implemented this functionality please
"supabase start" never worked on any machine for me.
you need the supabase cli for selfhost, but you propably go with cloud, so its not for you
seems like it not compatible with expo 51
Hey, have you found something that works?
I am stuck here too
@@alberttarkaa6589 yes, i've did it. Later I can link my code that works (if not forget)
google sign in authentication not working on realease apk
Have you registered the Client ID with the release SHA-1 certificate fingerprint?
Seems in iOS is not woking, it reports [AuthApiError: Passed nonce and nonce in id_token should either both exist or not.]
im having this same problem
@@williamliu796 Have you solved it? I'm looking to firebase now
Yes, there is currently an issue with iOS that's being worked on. Please follow along here: github.com/openid/AppAuth-iOS/pull/788
hi@@Supabase , the issue you linked to seem to be fixed, when can we expect it to work?
@@Supabase Does it work now ?