Open wyvern800 opened 3 days ago
Hello! I'm sorry you're experiencing this issue. I just tested it locally and was able to get the correct results.
How are you using it? Could you provide a basic reproduction?
Also, I notice you're using @clerk/clerk-sdk-node
. We advise migrating to @clerk/backend
for pure Node projects or @clerk/express
for Express projects.
Preliminary Checks
[X] I have reviewed the documentation: https://clerk.com/docs
[X] I have searched for existing issues: https://github.com/clerk/javascript/issues
[X] I have not already reached out to Clerk support via email or Discord (if you have, no need to open an issue here)
[X] This issue is not a question, general help request, or anything other than a bug report directly related to Clerk. Please ask questions in our Discord community: https://clerk.com/discord.
Reproduction
#
Publishable key
pk_test_ZXhvdGljLWNyYWItNzUuY2xlcmsuYWNjb3VudHMuZGV2JA
Description
Steps to reproduce:
Try calling 'getAuth' from the lib, in dev mode
Expected behavior: will only return:
{ ... [1] sessionId: 'example session id, [1] userId: 'example user id', [1]
seems like everything is null, it was supposed to come with a userId and a sessionId.
Actual behavior: will only return:
{ [1] sessionClaims: null, [1] sessionId: null, [1] userId: null, [1] actor: null, [1] orgId: null, [1] orgRole: null, [1] orgSlug: null, [1] orgPermissions: null, [1] __experimental_factorVerificationAge: null, [1] getToken: [Function: getToken], [1] has: [Function: has], [1] debug: [Function (anonymous)], [1]
seems like everything is null, it was supposed to come with a userId and a sessionId.
Environment