Thanks for including signup bro, everybody can do signin with the docs. The problem with firebase auth + next-auth is the signup
@harveyscodebase4 күн бұрын
Locally sessions arent working for me and the api request is just getting cached with a 304 error on the session the logs arent super helpful with this is this a chaneg is session provider I need to disable caching or can I make the cnage
@allankisembo59345 күн бұрын
you're too fast😭
@erickmaraz975311 күн бұрын
Thanks a lot for the tutorial! How can we achieve seeing the google signed in users in the firebase console? I think that is a great feature when we use firebase auth alone, but how can we achieve this together with nextauth?
@TheRealMxnny17 күн бұрын
Finally, someone that explain it in the most simpler manner! Thank will subscribe please do more Firebase Stuff & supabase
@DiegoCarreiraFr23 күн бұрын
Awesome video! Simple, direct and just what I needed! 👏
@FangerZero27 күн бұрын
1:20 thanks this is what I've been looking for, for the past week!
@jamesmac5902Ай бұрын
'client_id is required'
@alexandergeorgesquire220Ай бұрын
can you make your text bigger?
@colinmiller1942Ай бұрын
it worked perfectly on localhost but when I deploy it to Firebase user sessions don't work at all. I'll be able to create an account fine but there's no way to log in and stay logged in. The NextAuthURL is set for the right production URL too. I don't get any errors on the client side or server side that indicate something is off. Any fixes for this?
@joaumleeАй бұрын
great video!! cleared out a lot of this for me. but for some reason, nextauth is not "creating" a session on sign-up... i've been stuck for a while with this bug lol :/
@dmitrytuz9701Ай бұрын
Thanks for your block of videos! In kzbin.info/www/bejne/pZi8mYuYqdd2gK8 you use sign In With Email And Password from 'firebase/auth'. after sign, you got new record in the table in Firebase Authentication console. If you use Google provider from next-auth- it didn't add any records in table while if we call GoogleAuthProvider from 'firebase/auth' does it. How to made that new records appear in table with google provider? Perhaps we gotta create Custom provider for it? Could you please prepare the video?
@GarethDown2 ай бұрын
THANK YOU!!! Without this it would have taken hours to find all those random places you have to click to set things up! :D
@codeNinja23202 ай бұрын
Netlify doesn't support ISG
@zofrenlepetitkopat29792 ай бұрын
Stuck with the +layout.server.js, TypeError: Cannot read properties of undefined (reading 'locals')... :_-(
@jogiwalamohit44332 ай бұрын
Can I deploy next app when I have firebase blaze plan?
@abdulrahmanmufarrah78832 ай бұрын
I wasted 2 days on this when the solution is in this video.. thanks man.. saved me an extra day 😂
@iancarr39232 ай бұрын
I agree with the comments that the video is excellent.
@yogeshshahi2 ай бұрын
In a deepest tone… GREAT🎉🎉🎉
@user-gy8bk9dm1j2 ай бұрын
Good video, unfortunately the approach leads to problems when you start using an api. Normally the Firebase SDK would automatically refresh the token, when its expired. Here this doesn't work, because we authenticated on the server. Apparently there is no easy way to refresh the token with this setup, so I have to rip out NextAuth :/
@neelnarwadkar5921Ай бұрын
Hey, did you find any solution to refreshing token. Or did you stop using nextauth with firebase?
@user-gy8bk9dm1jАй бұрын
@@neelnarwadkar5921 The solution would be to refresh the token in the jwt callback with an API-call to Firebase. But if you build a client-based app, I don't think using Next-Auth in combination with Firebase makes sense, thats why I switched to using only Firebase and I'm very happy with it.
@neelnarwadkar5921Ай бұрын
@@user-gy8bk9dm1j hey can you help me with how you used just firebase and refreshed tokens
@saulotarsobc2 ай бұрын
2:39 /blablalba 😂😂😂😂😂😂😂😂
@AndriusLau2 ай бұрын
When we can expect video of Nextjs and Docker?
@saigunavanam58012 ай бұрын
awesome video brother can make with adapter with user sign in and for sign up with next auth? i was suffering with adapters , with email and password adapter is not working brother
@user-vr8lg4mu1g2 ай бұрын
it was great video brother , can you do video user authentication with adapter like creating user and sign store in database by using adapter delete and update like brother it help us a lot
@kelvenraymond84442 ай бұрын
Hi, adapters doesn't work with email/password provider (firebase from your next video). Nothing has been created in the firestore. Have you any tips for this issue ? I commented the sections, provider work, but when I uncomment the adapter, not working...
@saigunavanam58012 ай бұрын
yes brother same issue it doesn't work with that y i don't know
@kelvenraymond84442 ай бұрын
@@saigunavanam5801 Yes, I finally opted for the version with Context/Provider instead of nextAuth in the case of email/password. In the case of Google Auth only, nextAuth with the adapter works well. It successfully creates user and account data in Firestore.
@CuongNguyen-jr9oq15 күн бұрын
same issue :(
@mrgaud3 ай бұрын
awesome job dude. Great tutorial. Subscribed
@LP53 ай бұрын
Thanks for sending super engaged traffic to our videos! Really appreciated!
@juliancoln61153 ай бұрын
Good Video, short and on to the point. Like it <3
@neelnarwadkar59213 ай бұрын
Hey any idea about how to get the firebase generated token in this? I need it as authentication headers for some express js apis.
@neelnarwadkar59213 ай бұрын
Anyone else got this error localhost:3000/api/auth/session 404 (Not Found) [next-auth][error][CLIENT_FETCH_ERROR] Does anyone know the solution? I have tried everything and also i have set the nextauth_url and nextauth_secret.
@classicaf3 ай бұрын
thank you
@MaxWis3 ай бұрын
Ive been having some big problems with firebase... For some reason whenever i make an app that does anything with the pages/api or app/api folder the cloud function it generates for you always times out. do you know of a way to fix this? :)
@MaxWis3 ай бұрын
I cant seem to get it to work on production, it keeps timing out when doing the api calls. does anyone know why or how to fix this?
@kirillvolsky90223 ай бұрын
I use auth v5 everything works fine when i sign in first time, but after signout, on next try sign in i would get an error "To confirm your identity, sign in with the same account you used originally." But i have only one provider this is google. I notice that with flag allowDangerousEmailAccountLinking: true on each sign in firebase will add new account user doc, I cleaned my firebase and still same problem, somebody can help ?
@fh3r34 ай бұрын
thanks! very clear!
@mikkelpetersen55294 ай бұрын
It is actually a huge misconception that Client Components are not rendered on the Server. They are in fact still SSR'ed. Just something to keep in mind. If you want them to truly not be rendered on the Server, you can dynamically import the Component and add ssr: false to the options.
@user-tz3bc3dl7g4 ай бұрын
HI! Thx for the video. Have you tried to enable App Check for Firebase? Official docs say to do it this way: const appCheck = initializeAppCheck(app, { provider: new ReCaptchaEnterpriseProvider(/* reCAPTCHA Enterprise site key */), isTokenAutoRefreshEnabled: true // Set to true to allow auto-refresh. }); But it works only for the client side, but signInWithEmailAndPassword we call on the server, so it does not use the app check token and I got: An error (auth/firebase-app-check-token-is-invalid.) Do you know how to handle it? Thx in advance
@user-tz3bc3dl7g4 ай бұрын
HI! Thx for the video. Have you tried to enable App Check for Firebase? Official docs say to do it this way: const appCheck = initializeAppCheck(app, { provider: new ReCaptchaEnterpriseProvider(/* reCAPTCHA Enterprise site key */), isTokenAutoRefreshEnabled: true // Set to true to allow auto-refresh. }); But it works only for the client side, but signInWithEmailAndPassword we call on the server, so it does not use the app check token and I got: An error (auth/firebase-app-check-token-is-invalid.) Do you know how to handle it? Thx in advance
@ionutsandu59134 ай бұрын
Thanks!
@edhahaz4 ай бұрын
Next, nuxt, sveltekit is all about server side rendering... not signals
@user-tl4ox3io1i4 ай бұрын
just straight forward! loved that
@HussainMurtaza-ov4ln4 ай бұрын
Sir! How can we store users with Googleprovider inside Authentication Tab in Firebase using Next-Auth. In your adapters video the users get store inside Firestore using GoogleProvider I want them to store inside Authentication tab Please help me
@dominiksiejka88584 ай бұрын
signInWithEmailAndPassword should only be called on the client side, as calling it in this manner may lead to potential issues.
@musabhussain36414 ай бұрын
wow! its so clear!! Amazing!
@SakthiCs4 ай бұрын
Specified "rewrites" cannot be used with "output: export" I got this error..how to solve this
@niranjans82174 ай бұрын
The session is not getting stored during signup. So what if the user need to use the web instantly after signup ? How can we setup signup with next auth?
@Namynnuz4 ай бұрын
Where's the other possibility, when you scoop out dynamic code and host it as lambdas?
@oscarascencio16364 ай бұрын
Hola se pueden ir listando los usuaios en el apartado de Authentication de Firebase y no en Firestore. Gracias
@ukaszStrzelecki5 ай бұрын
You have to rethink your recommendation of Firebase Hosting :) I've just build a simple app with Next.js and I have a hard time with Firebase deployment. The same code works flawlessly on Vercel but not working on Firebase at all. On firebase I don't have access to server logs (or I don't know how to find it) so I don't know what is happening. I will be great if you make a video about debugging deployment on firebase hosting and how to find a problem. Cheers
@FangerZero27 күн бұрын
I finally figured this out the 1:20 time stamp was the last part I needed to complete my Firebase SPA.
@ukaszStrzelecki5 ай бұрын
Thanks man! I've watched a lots of tutorials and yours are really great! Fast, complete, without unnecessary bullshit!