mirror of
https://github.com/better-auth/better-auth.git
synced 2026-10-19 11:24:57 -05:00
Bereket Engida
892bdd6bbc
validateAuthorizationCode failures were logged with an empty message
and no provider id, and a provider that answers 200 with an error
body (Slack `{ok:false,error:"invalid_code"}`, or an
`error`/`error_description` pair) produced no log at all until the
unrelated getUserInfo step failed later. Add the provider id to the
catch-site log message and log when a resolved token set has neither
accessToken nor idToken, using only the provider-supplied error
fields (never the raw token response, which may carry secrets).