github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 07:18:56 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #2023] Update image after provider log-in? #9011

New Issue
Closed
opened 2026-04-13 04:16:17 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-13 04:16:17 -05:00
Owner
Copy Link

Originally created by @jillesme on GitHub (Mar 27, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/2023

Is this suited for github?

  • Yes, this is suited for github

Is your feature request related to a problem? Please describe.

When you allow emailAndPassword registration, the image is usually empty. When someone later uses a provider log-in we do get an image back. Should we update the image field is it's empty or null?

Describe the solution you'd like

  1. User signs up with email / password
  2. User profile image is empty
  3. User uses provider (e.g. Google OAuth) the second time
  4. User profile image is populated

Describe alternatives you've considered

I can of course manually populate image based on the data returned by await authClient.signIn.social(..). However, it seems like this might be nicer to have "baked-in". The reason being:

  1. If you sign-up using a provider you get an image
  2. If you sign-up using an email and password, but later using a provider, you get no image.

It might be nicer just to have a standard "if you sign in with a provider, you get an image"

Additional context

No response

Originally created by @jillesme on GitHub (Mar 27, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/2023 ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. When you allow emailAndPassword registration, the image is usually empty. When someone later uses a provider log-in we do get an image back. Should we update the image field is it's empty or null? ### Describe the solution you'd like 1. User signs up with email / password 2. User profile image is empty 3. User uses provider (e.g. Google OAuth) the second time 4. User profile image is populated ### Describe alternatives you've considered I can of course manually populate `image` based on the `data` returned by `await authClient.signIn.social(..)`. However, it seems like this might be nicer to have "baked-in". The reason being: 1. If you sign-up using a provider you get an image 2. If you sign-up using an email and password, but later using a provider, you get no image. It might be nicer just to have a standard "if you sign in with a provider, you get an image" ### Additional context _No response_
GiteaMirror added the locked label 2026-04-13 04:16:17 -05:00
GiteaMirror commented 2026-04-13 04:16:18 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Apr 12, 2025):

supported from 1.2.6-beta.13

<!-- gh-comment-id:2799038813 --> @Bekacru commented on GitHub (Apr 12, 2025): supported from `1.2.6-beta.13`
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label locked
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#9011
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?