The guide and document are awesome. Thank you. 1. How to handle refresh and access tokens in real app scenarios (Retrieving and revoking a session in real-world scenarios). 2. Implementing pagination with infinite scroll using Supabase PostgreSQL.
@@xeooox Thank you so much for the compliment. What exactly would you like to see about handling refresh and access tokens? Using Supabase, you shouldn't really have to worry about handling refresh or access tokens (unless you want to revoke it like you mention). Retrieving the tokens should happen automatically by the SDK, and you should never have to worry about or handle it yourself. Are you finding yourself to be in a position where you have to handle it by yourself?
dude, you saved my day!! It was pretty non-obvious for me before where I need to use android service id vs web service id, and why it is web service id for android if I use native sign in... mobile dev is slightly confusing, but thanks a lot!!
Supabase have to add the crucial feature for all real word app like transaction native feature or batch on db. Otherwise we can't chose supabase to to make a good apps.
Actually, transaction is supported through Postgres functions. You can create a Postgres function and call it using the .rpc method from the client. Batched writes have been always possible using the standard insert or upsert method on the client libraries!
For a big project that need many transaction operations which take two or three table with many field is not easy. Maybe you have your reason but that lack of this features is a big issue.
We have a wide range of Auth features that we offer with it like MFA, SSO, OAuth with 19 different providers, and we need to sustain it. It comes with a pretty generous free tier though.
thanks! i have an issue redirecting the users to the right page, i want to to redirect the user to continue the onborinf and completing the user information when they clic on sigup and if they clic on login with google they will be redirect to home. do you have anyidea on how to achieve this ?
Three different client IDs all have different purposes, and they are all required if you want to support all web, iOS and Android. As shown in the video, the one you paste into the Supabase dashboard is the web Client ID.
@@Supabase I did everything as in the video, after clicking the button the method works, but Google gave the following error: "401 invalid client", "flowName=GeneralOAuthFlow". I see this error only on the web when I open the application through a browser; in the Android emulator everything works fine. I will be glad for any hint! Thank you! this numbers is after Auth displayed in page, i don't know how display user Gmail.
Flutter web changes the port every single time you run it, so it's either specifying the port like in the video, or adjusting your code every single time you run it locally.
It seems I haven't found a tutorial for Sign in with Apple using Supabase and Flutter. By the way, how can I link multiple OAuth logins to the same account? I mean binding both Apple and Google to the same account. Of course, it should also work for Web and Android
Creating a Firebase project always creates a GCP project in the background, so maybe you are looking into the wrong GCP org or something. Navigating through GCP console might not be easy if you are not used to it, but look around and you should find the corresponding GCP project!
Google sign-in on the web with Flutter does not use the google_sign_in plugin, but rather uses supabase.auth.signInWithOAuth() method, so it will not be affected by the deprecation.
If you could precisely share the exact error message and the platform you are running it on, I might be able to assist you better, but it most likely is due to not configuring one of the configurations correctly. There are iOS, Android, and Web client ID that you need to handle in order to implement Google sign-in, which is quite confusing, so take you time, watch back the video, and make sure you have added all the correct configuration in the correct place.
@@dshukertjr I am only using an Android client, and I have done the exact same thing and copied the exact same code from the video. the one thing I excluded was web client and ios client
@@devagarwal3250 Okay, well creating a web client ID is a requirement for supporting Google sign-in on Android. At 03:19, you can see me adding the Web Client ID into the dashboard.
The login on iOS works perfectly but the one on Android doesn't work. It keeps giving me the same error [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: PlatformException(sign_in_failed, com.google.android.gms.common.api.ApiException: 10: , null, null)
That error most likely means that you are providing the wrong SHA1 certificate fingerprint to GCP. Double check that you are providing the correct one, and you should be good to go.
