Possible bug (remix): backend getAuth returning null but frontend useAuth returning logged in user #1885
Replies: 5 comments
-
I'm observing the exact same thing - as soon as I've moved into production, Did you have any luck? |
Beta Was this translation helpful? Give feedback.
-
Ahh right okay so it just simply doesn't work, as I think you noticed over in sO haha. For anyone else - this link has the solution. |
Beta Was this translation helpful? Give feedback.
-
Having the same issue. Edit: Ah you're supposed to do |
Beta Was this translation helpful? Give feedback.
-
I was using @clerk/nextjs (4.25.7) and had a similar issue. Upgrading to version 4.29.3 resolved the bug. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Pinging before i dive in further to see if anyone else is seeing this.
I have a Remix 2.0.1 Express installation with Clerk 3.0.6. Clerk works fine locally with the "development" Clerk environment, but when i deploy and use the "production" Clerk environment, I can sign in as a user in the frontend without issue, but the Remix backend does not see the user: getAuth() says the user is signed out.
Anyone have thoughts on what might be causing this?
Beta Was this translation helpful? Give feedback.
All reactions