Under the pre-1.0 API resume on app launch happened by calling into the SupabaseAuthState.recoverSupabaseSession(). A version of that method still exists on SupabaseAuth but it is now private and only accessed through SupabaseAuth.didChangeAppLifecycleState with a "resumed" AppLifecycleState value. I can't see where that is being called. In the Supabase Auth UI project I created a method which calls SupabaseAuth.instance.didChangeAppLifecycleState(AppLifecycleState.resumed). I can get it to resume the session but there are a couple of problems. First, the _recoverSupabaseSession() is async but didChangeAppLifecycleState is not so there is no way to await for the return or to know what the return value was. Second, it feels like this is supposed to be initiated somewhere else but I can't determine where. My workaround right now is to call this right after init, add a button to a splash screen to go into the real part of the app, and then only click that button once I see that the session has been restored in the output. That is all obviously not ideal.

Is there a plan to have this reload exposed elsewhere in a way we can wait for it at our app level or expose the recover method itself for direct initiation?

• refactor error handling into a single function

• example: remove unneeded accesstoken should we remove it from the readme?

• add a wait for email screen ForgetPassword / MagicLink: onSuccess go to wait_for_email. (A snackbar is forcefully also emitted, seems a bit redundant) What should we do? Also why does MagicLink have a special onSuccess handling?

SignIn: OnError('Email not confirmed') go to wait_for_email. Note that we do not handle the other errors in that case. (the snackbar is not called any longer) Should we have a special callback for email_not_confirmed?

SignUp: how do we redirect to wait_for_email? We were calling sign_in just after sign_up which had multiple benefits in my option: provide the same 'Email not confirmed' error, and signin user if there is no email confirmation or if their account already exists. Happy to fix that also if you have a direction.

Currently, the widgets are configured to support apps that are using named routes. I would like to be able to use regular navigation as well using this library.

Thanks @FatumaA again for all the amazing work. The widgets that you implemented are very intuitive and easy to work with! I wanted to tweak the widgets a bit so that the border style will inherit the user's theme. Also wanted to change the package name if it was okay with you!

Hi,

I just wanted to say thanks for a great package we can use to simplify authentication with. It really does make it go faster and I know I have qualified devs working on auth for/with me. Sometimes it's not an easy thing, especially when I'm new to flutter.

So my request is for the ability to override, or allow us more options/customization of SupabaseAuth. Couple things come to mind when I say this. 1. I was working through the chat app tutorial, the branch with auth, and when a user is added to the table, a trigger then adds a couple fields into the profile table. One of the things that's supposed to be added to profile's page is the username from auth.users. Well the username now comes from the raw_user_meta_data jsonb column. So the email and pass get's inserted, but no username. And there is no way to add the username to the metadata column in flutter with this package. I ended up just creating another trigger and function that add's a new username into metadata column when inserting and then taking that and inserting into the username column in the profiles page.

Here's the code to do this if anyone would be interested and came across the same issue as me. Took me a little bit to figure out how to handle the jsonb in a trigger/function like this, but did finally get it working. So the email is just used for the username as well. This function add's it into the same table but in the metadata column, and then the trigger/function from the tutorial picks that up and inserts it into the profile table along with other info.

create
or replace function handle_new_user_metadata() returns trigger as $$
    begin
          update auth.users
          set raw_user_meta_data['username'] = to_jsonb(auth.users.email)
          WHERE auth.users.id = NEW.id;
        return NEW;
    end;
$$ language plpgsql security definer;

DROP TRIGGER
  IF EXISTS on_auth_user_created_meta ON auth.users CASCADE;

create trigger
  on_auth_user_created_meta
after
insert
  on auth.users for each row
execute
  function handle_new_user_metadata();

It would be a lot easier though if we were able to do this from dart/flutter. I see there is already the capability in the supabase client, but we can't access it from this package. Only the email and pass can be used when calling to create a user in registration. So that would be nice to override/ or just have all 4 of the parameters that are in the supabase sdk create user method.

Second would be the navigation. I'm using riverpod and go router for my nav. Riverpod listens for auth state changes, then go router listens to riverpod to trigger it to log the user in/out according to their auth state. But then when there is code for a second navigation, it messes with the whole flow. Maybe an option to use your own router and logic, or use what's baked in?

These are just some suggestions. I love the idea of being able to quickly get auth going so I can get on with the actual business logic a client needs. You have done a wonderful job on that and just wanted to say I appreciate it a lot.

As environment in pubspec.yaml says, this package uses Dart SDK version 2.17.0 or higher,

environment:
  sdk: ">=2.17.0 <3.0.0"
  flutter: ">=1.17.0"

so enhanced enum feature is available.

Instead of defining functions like capitalizeName, getIcon, getBtnBgColor inside _SupaSocialsAuthState class, this PR includes such properties in SocialProviders enum.

I think now that supabase_flutter v1.0.0 is used, we can release v0.0.1 of this library. It is still in v0, so we can still introduce breaking changes if we need to.

What kind of change does this PR introduce?

Updates the code to use supabase-flutter v1.0.0

Fixes https://github.com/supabase-community/flutter-auth-ui/issues/33

What is the current behavior?

The code is still using developer perview of supabase-flutter

What is the new behavior?

The code uses supabase-flutter v1.0.0

Feature request

Is your feature request related to a problem? Please describe.

There are number of breaking changes in gotrue-dart side of things, so they should be upgraded over here.

• Code cleanup
• Solidify onSuccess and onError
• Fix auth flow for anything using Deeplinks
• Add metadata fields to be able to pass metadata on signup form
• Release a new version 🚀

• Users can decide how to react after the Supabase action finishes :
  • Add onSuccess callback instead of the success alert for most components.
  • Add onError callback instead of the error alert for most components.
  • For example callbacks are needed in order to display a page asking the user to verify their email when signing up or using a magic link.
• Fix some typos.
• Fix missing redirectUrl.
• Add a CircularProgressIndicatoron some buttons.
• Reword some buttons to "Continue" when they both signin and signup. (Magic Link & Providers).
• Call signIn after signUp to handle cases where user already exists (or when email verification isn't set).

Hi,

if the feature make sense for the library, do you have an idea of how we could provide persistence between screens?

Probably we should support two use cases:

• persistently store the email to reuse at next sign in
• temporarily store email / password between the relevant screens

Which screen should support that? ie does it make sense for reset password?

Passing a default initialEmail/initialPassword is a bit annoying, cause with go_router when changing screens the supabase components may not change instance and those not use the new initialEmail/initialPassword

I've taken a look at this library and played with it a bit.. Here are a few suggestions to improve it..

1. Show user how to query Supabase after login.. I don't understand how I'm to use the authenticated user from this package in a Supabase request.. When using the base supabase_flutter library, I got caught out intializing two Supabase instances which made all my calls fail when RLS was implemented.
2. Show the deep linking in action, actually working and how to set it up.. This is something I'm still trying to understand..
3. Show Logout Flow.. I logged in using this package, but there was no logout button.
4. Show restored session flow.
5. Show how the new 1.0.0-dev OnAuthenticated/UnAuthenticated State from Supabase package should be used..

This is a great package and it helped me solve one flow problem.. Thanks.

ReadMe should show how to initialise the project when using this library. You don't need the supabase_flutter dependency directly if only using the auth ui lib