Closed slackermorris closed 3 months ago
Hey @slackermorris, Let's try something quick can u do this ?
<SignIn routing="hash" />
@panteliselef Yup that solved it just fine. I'm not too versed in routing. Would you mind explaining how the above solution has fixed my issue?
Here is what the official docs say about routing in Clerk components.
I recommend hash routing because astro performs full page loads and components with path routing will flash in the screen as a whole new document loads.
Probably the issue with your original code was that the /sign-in
route was not a catch all route.
I'll be closing this as the issue seems to have been resolved.
Hi there,
Context
Thanks a bunch for this SDK.
I am at a loss to best describe what my issue is, mostly because the ready-to-use magic of Clerk sometimes makes it difficult to know what needs to be configured manually. And, to be honest, I've hit so many set backs elsewhere that I and a bit deflated and am hoping for an answer that doesn't require me to scale Everest myself for the understanding. Lol. Yes, I am being lazy, but something about "save time here to spend it elsewhere".
Whenever I try to sign-in using the
SignIn
component I am redirected to afactor-one
page (which I have not implemented). I would have thought that theSignIn
component would handle password authentication for me, etc, so I am unsure what I need to do? Any clues?Relevant Files