Bug in user profiles connected via "Sign in with Apple"

When using Sign in with Apple, the user profile value for the field “email_verified” is set as string “true” instead of just true.

Some encoders (like in GoLang) do have problems in unmarshalling fields that are of type boolean if the field is returned as string.

Wrong:

"email_verified":"true"

Right

"email_verified":true

We don’t have this problem with other social providers or regular email password authentication, which makes it more difficult as the encoder in Go can be configured to accept strings for booleans or booleans, but not both.

Thanks a lot for providing that feedback! Have you been using some quickstart of ours when implementing that? Any links will be helpful cause this way I’ll be able to track the responsible team quicker as there are a few teams handling our “Sign in with Apple” stack. Thanks!

I followed these two guides:

1 Like

Perfect! Thanks a lot for letting us know! Will reach out to the docs authors in a minute!

Just relayed your feedback. Should be fixed shortly!

1 Like