supabase.auth.linkIdentity does not return raw_user_meta_data
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go, javascript
- Domain
- api, authentication
Research direction
No files or tests are named. Start by reproducing the listed flow with supabase-js 2.44.2: sign in anonymously, call linkIdentity, and compare raw_user_meta_data in auth.users with the signInWithOAuth result. Done means linked identities return and store the expected metadata consistently.
Written by the indexing model from the issue text.
Description
Bug report
- I confirm this is a bug with Supabase, not with my own application.
- I confirm I have searched the Docs, GitHub Discussions, and Discord.
Describe the bug
When calling supabase.auth.linkIdentity using the JS client, it does not return and store the raw_user_meta_data that you would normally get when using supabase.auth.signInWithOAuth:
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
- Sign in an anonymous user
- Try to link identity with supabase.auth.linkIdentity
- Check the raw_user_meta_data in auth.users
Expected behavior
It should return the metadata just like an oauth sign in.
Screenshots
When using supabase.auth.signInWithOAuth, it returns the raw_user_meta_data:
When using supabase.auth.linkIdentity, it does not return it:
System information
- Version of supabase-js: 2.44.2
- Version of Node.js: 20.15.1
Additional context
It would be best if it can be returned as I want my postgres trigger to automatically add the full_name and avatar_url to my public.profiles table once the user's anonymous account has been converted to a permanent account once they've signed in.
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 764
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 39
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from supabase/auth
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Similar issues
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
blinklabs-io/bursa#904 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yanet-platform/ipfw-go#129 ·
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100