You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All of elements putted into SignedIn wrapper still appear on the page till manual refresh on page
I am not sure if this is my implementation or just a bug
If its not a bug i would appreciate some help
<ClerkLoaded> <SignedOut> <li class="px-4 first:py-0 last:py-0"> <a href={Paths.signIn} on:click={handleNavStatus} > Sign in </a> </li> </SignedOut> <SignedIn > <li class="px-4 first:py-0 last:py-0"> <SignOutButton /> </li> </SignedIn> </ClerkLoaded>
this code is from component that is being rendered in +layout.svelte
I've tried doing onclicks with goto, location.reload, nothing seems to help with it
The only possible solution is to use <UserButton /> but it doesnt suit my needs
The text was updated successfully, but these errors were encountered:
<SignOutButton signOutCallback={handleSignOut}> Sign Out </SignOutButton>
first you add callback to your SignOutButton and in the callback you call goto method to some non existing route for example '/sign-out'
and then in the hooks.server.ts file you add:
const handleSignOut: Handle = async ({ event, resolve }) => { if (event.url.pathname.startsWith('/sign-out')) { return new Response('Redirect', {status: 303, headers: { Location: '/' }}); } return resolve(event); }
and add it to your handle
resolved my issue
Step to Reproduce:
I am not sure if this is my implementation or just a bug
If its not a bug i would appreciate some help
<ClerkLoaded> <SignedOut> <li class="px-4 first:py-0 last:py-0"> <a href={Paths.signIn} on:click={handleNavStatus} > Sign in </a> </li> </SignedOut> <SignedIn > <li class="px-4 first:py-0 last:py-0"> <SignOutButton /> </li> </SignedIn> </ClerkLoaded>
this code is from component that is being rendered in +layout.svelte
I've tried doing onclicks with goto, location.reload, nothing seems to help with it
The only possible solution is to use
<UserButton />
but it doesnt suit my needsThe text was updated successfully, but these errors were encountered: