Improvement in the documentation - PARAMETERS FROM CALLBACK BODY

[masdeval]

When you write "The PARAMETERS FROM CALLBACK BODY should be filled with the urlencoded body you receive on the endpoint from Apple's server" you mean that the backend must extract the claims from the id_token and send them, right? We can see in the AuthorizationCredentialAppleID:parseAuthorizationCredentialAppleIDFromDeeplink method it gets the user information doing

final user = deeplink.queryParameters.containsKey('user') ? json.decode(deeplink.queryParameters['user'] as String) as Map<String, dynamic> : null;
so it is expecting a parameter called user which, of course, is not present in the body sent by Apple.

I do not know if I misunderstood the actual documentation and all of that interpretation is embedded in the snippet "should be filled with the urlencoded body" but I spent a considerably amount of time to figure all these out.

[jacsdev]

Were you able to make it work? I'm facing a similar situation

[masdeval]

I was implementing a login for a flutter app. I was struggling with the fact that Apple sign in , differently from Google, does not send any information about the user, not even the email. Despite all my attempts of processing its return in a backend Java REST url ( what I mentioned before indeed works that way) it did not send user information. When the user choose login via Apple in the app, I open a dialog to allow the input of all personal information which I save in the database. Although I still validate it’s password using Apple

[jacsdev]

In my particular case is that when in my backend I receive only id_token and code, and when I send that to the android app through a temporary redirection with an "intent://callback", it tells me null check...