Provide given and family name during Apple native sign in about flutter-auth-ui HOT 4 CLOSED

When a user signs in using Apple for the first time for the app, Apple will provide the full name and email address if the user approves it. The full name and email address will be available in the raw user metadata the same way as Google login, and you can use triggers to store them in any table that you would like.

If you are not seeing the full name and email address after completing the Apple sign in, it means that the user has signed-in on the same app before.

from flutter-auth-ui.

I don't see this happening, even in production. I even added analytics logs to my app whenever someone signs up using apple, and the metadata have never been there. There are also open issues on supabase. The only thing that is working is this workaround that others have proposed and that I am using now and have started in my fork.

from flutter-auth-ui.

Could you link the issues that you have found discussing this topic? If it's an existing bug, we should fix it the proper way. The Supabase auth server should be storing that information on the user's metadata.

from flutter-auth-ui.

Here the references:

• same behavior in the js library: supabase/supabase-js#899
• older issue where you answered as well: supabase/supabase-flutter#545

However, I've seen this comment from you:

@takuya-ohmuro Currently, Supabase does request for email and full name scope when performing Apple sign in. You can retrieve the full name like this:

final response = await supabase.auth.signInWithApple();
print(response.user?.userMetadata?['full_name']);

But the method signInWithApple does not exist anymore. Instead, the native apple sign in is used and then the signInWithIdToken.
I don't even know why it should work, because the native apple sign in returns the full name in the credentials, but these credentials are only used for the identity token and the name is thrown away. Maybe I don't see the hidden magic here. Also, I don't know how the old function worked, maybe you know more.

Another option that I have not tested yet is at the _nativeAppleSignIn() call, the return type is ignored. Per haps that auth response holds the metadata and we would then have to call supabase.auth.updateUser with that metadata, but would still not be a pretty way to handle this.

from flutter-auth-ui.