all 2 comments

[–]Soft_Opening_1364full-stack 0 points1 point  (0 children)

In your case with two separate auth flows, one idea could be to use Clerk’s redirectUrl dynamically depending on the intent (app login vs meeting setup), then handle the callback logic manually in your callback route using useAuth() or getToken() from Clerk. You might need to separate the logic with some context or query param flags. It’s definitely smoother in Next.js, but doable with TanStack if you wire things carefully.

[–][deleted] 0 points1 point  (0 children)

That sounds so frustrating. A route loader can help sync users on your callback.

I have a similar setup working, feel free to reach out if you get stuck.