Based solely on the information you provided (aka without actually trying it for myself) I would say that the likely cause of the situation is that you’re not including the openid scope.
Both the email and profile scopes are associated with OpenID Connect (OIDC) specification and signal that you want to have access to associated user information. However, a request that wants to have OIDC behavior should signal that by including the openid scope, otherwise, the exact response behavior is unspecified.
You should try using scope=openid email profile.