Yiannis Panagidis
Yiannis Panagidis
> Had the same issue but with `CredentialsProvider` instead. > > Changing the route to not use `edge` also fixed the issue for me, but I would like to use...
> > Yeah same for me, I have made sure everything else is edge compatible so it's a bit of a shame > > Unfortunately, it's still a beta version...
> Just FYI (and per #9966), I can confirm that the issue does not happen in production. I never actually tried it in production as I (wrongfully) assumed it would...
is there any way to achieve this without setting a static height ?
@katungi if you get on it and you need any help I would love to help out!
Hey guys, you ever found a solution to this? I realise it's not very important, just asking incase either of you came up with anything before I give up on...
That's what I found as well, but didn't quite get it to work. Gonna look into those a bit more and get back to you!
https://github.com/vercel/turbo/discussions/4304 I tried this with no luck. long story short anything i import in a package based on path alias it comes back as any in any app that uses...
I should also mention that my issue (https://github.com/nextauthjs/next-auth/issues/9869) originated with t3 turbo but i reproduce it with a normal next app. Basically any time the auth flow is not successful...