thanks for commenting with that solution i would of prob given up lol

bro 🔥🔥🔥

Ty!

I'm still getting an error in the console saying "app.auth()" is not a function. Any chance you could help me with what i'm doing wrong? import { initializeApp } from "firebase/app"; import 'firebase/compat/auth'; const app = initializeApp({ apiKey: process.env.REACT_APP_FIRBASE_API_KEY, authDomain: process.env.REACT_APP_FIRBASE_AUTH_DOMAIN, projectId: process.env.REACT_APP_FIRBASE_PROJECT_ID, storageBucket: process.env.REACT_APP_FIRBASE_STORAGE_BUCKET, messagingSenderId: process.env.REACT_APP_FIRBASE_MESSAGING_SENDER_ID, appId: process.env.REACT_APP_FIRBASE_APP_ID, }); export const auth = app.auth(); export default app;

Legend

I’m so glad I found this video I was trying to build the user login feature using Firebase for a project.

ass kisser

In my case it's reverse...when I watch something ...that exact thing I have to apply next day to solve issues🤣🤣

You are a life-saver

life saver, thanks for sharing

Thank you so much

Thanks! I was getting stuck on this for sure. btw Are you sure that this is the correct way to do things now?

@@MiikaKontio No worries, not sure if it's the "correct" way to do things but it's how I was able to get it to work

@@GrayFox391 i mean is it safe? I dont want people to see Pages they are not supposed To see

@@MiikaKontio If a user isn't logged in then they won't be able to access the routes

Thank man. I was stuck here for hours. Tried React Router Dom documents and all, but none of them worked. Thank you so much again.

If you make a fortune because of Kyle's tutorials, make sure wire part of it to Kyle's bank accout to support Kyle continuing making awesome tutorial videos !!!

sure you can support him on Patreon.... the link is in the video description

@@amankaushik5833 yep, but i dont have money now...

@@maskman4821 Its a good idea

@@amankaushik5833 Obs: 1 Dollar in Brazil is 5.75 Reais

do all the functions still work? or is it outdated? thinking of coding along

came here to say the same thing. thanks man! react-router-dom's documentation is pretty good too, everyone should check it out for more details

m stuck at 24:35 saying that 'Failed to create an account' eventho the password is same and more than 6 characters. Any idea?

Assalamu alaykum @@muhammadaqlan1649 I had the same error and it was because i imported the signup method as { signup } instead of { signUp }

@@muhammadaqlan1649 I had the same issue. My resolution had something to do with the env.local file. I hard-coded the values to authenticate with Firebase config and it fixed the issue.

Thank you for sharing! I had this same problem too!

Best I can say is: Firebase docs, or Fireship io next Firebase course.

yes very much wrong with context and in app.js with router-dom dont work

yea i know i want say dont try make project with old video only 2022-23)

Can we please get this updated with NextJS

It's mostly the same, the biggest change is way you create protected routes in React Router v6. Dennis Ivy made a great video about how to make it in v6: kzfaq.info/get/bejne/aNFogc-Wq9CrZ30.html

Upvote! This solved my problem. I had to close and npm start again. Many thanks, Tom.

3 months later and this solved my problem as well. Thank you!

Hmmmm! Will give it a try

I tried this but it still says that my api key is not valid. I plug in the api key directly instead of the "process.env..." and it works. Not sure what is up there.

@@Darclay24 I'd try console.logging the process.env.REACT... to see if that is working. I think the variables must start with REACT_APP_ or they will not work.

what should i do in the config?

same problem

just create a realtime database in firebase and after creating the database reload the page where you see the config. The link will appear. It worked for me.

Yea its easy to see if inside catch you do catch(error) { console.log(error) } then google says if email already exists or if password to weak and other problems :)

Thank you! I was wondering what I was doing wrong until I read your comment!

@@TheLigitaksas thank you very much I was looking for this

Legend! Thanks king

Thanks, this is exactly what I was missing!

Thanks man! Killer hint!

After struggling and constantly adding my own style and reading docs to do even the most basic thing, I have come to the conclusion that writing css myself is far more better and under my control.

OH GOD THANK YOU

YES! THANK YOU!

I didn't know about inputRef so I used the e.currentTarget.elements in handleSubmit 🥲

For other firebase newbies you might find this video helpful for working with version 9 : kzfaq.info/get/bejne/rMmhodyi3LasY4U.html

Not to mention React Router v6

You figured it out in 3? Lucky… 🥲

god bless you

Thank you so much!

I got failed to create an account at 24:35 please address this issue... :(

Then i have app.getAuth is not a function T.T

same thing here stuck for couple hours on this error @@oxpey4473

unfortunately, you might wanna not use this video as reference anymore. The version of firebase used in this video is different and firebase v9 was released on sep 1 2021. the syntax, the functions, etc have all changed and its a waste of time trying to troubleshoot. Use the tutorial docs provided by firebase for a more up to date reference.

Could you please share with me your updated version of this code? i've been strugling for weeks and almost gave up on firebase auth

@@abdulazizaljaadi5579 function notifyAccountCreated() { setNotification('Account created'); setTimeout(() => { navigate('/signin'); }, 2000); // Redirect after 2 seconds }

HUGE thanks for this. :)

I did, thank you

Thank You!

THANKS MAN

yeh right ..so will it work if we continue the lecture?

Where in realtime database section? Do we have to create a new database?

Huge help, Thank you!

Thanks for your kind comment you save my time to traveling with errors

@@jonghyeonko3275 happy to help!🙂

I keep getting the error in my console: "Your API key is invalid, please check you have copied it correctly." @Web Dev Simplified

@@fauxeditor6663 When I use the API key string directly in firebase file it works but not when it is used as my env variables..

Same issue here, has anyone figured this out? In development everything works fine, but when i try to deploy, it deploys as a blank page and the console says "Your API key is invalid, please check you have copied it correctly."

I think it is because in the try {} block you have "history.push('/')" that redirects you to Dashboard component and then you try to set "setLoading state" to the Login component that now is unmounted.

Hey Jeremy, were you able to figure out why this happens? I have the same error and commenting out the loading seems to work for me too. Would like to find out how to fix it permanently though...

@@kjro23 Hey so I was still receiving the error. I took what Lavinia stated and just moved the history push outside of the try{} and after the setloading(false). That resolved the error and the history.push still works. :D. Hope that helps setLoading(false) history.push('/profile')

@@jeremydiaz6494 i dont think you can put history.push(" outside the try block, if there is error on your login, the the catch block will not work properly

Hero!

did it?

@@demetrissergides7059 I ended up doing another vid sign in

Wondering how to find this too. Can't figure out where to find it Did you ever figure it out?

@@stephanieraymos4675 yes you must follow lots of videos, this one and a few more about sending the user a email Verificacion and after add Google sign in etc etc

@@tod670 I actually figured out you don’t even need the database URL anymore. It’s deprecated. My site is working fine without it.

Kyle is everywhere, he can read your mind, and creating awesome content to help people, he is amazing !!!

God's work right here

Here's the solution if anyone is still looking for it. It was provided by someone called Lavinia Ţole in this comment section: "I think it is because in the try {} block you have "history.push('/')" that redirects you to Dashboard component and then you try to set "setLoading state" to the Login component that now is unmounted. I moved setLoading(false) after the await function and before the history.push('/') and the error is now gone."

@@somkl7617 Thx! :)

@@somkl7617 but if the login error, that will never loading set to false! you have to put that after setError in the catch block as well!

There has been an update to Firebase so now I do not think we have it anymore...

Hi, I'm trying to understand why it happens.. I tried what you suggested and I still get this error in the console. Could you please explain again? Thank you!

@@nivmonovich7976 I don't know how i can explain better, not that my explanation was perceft just i don't know how to do it. if you don't know about mounting/unmounting components you should look them up, it might help you understand better. it is not exactly same but we can think like we are trying to edit something that no longer exists.

@@ylmazcandelen3121 Thanks! But as I understood the return unsubscribe in the end of the useEffect supposes to 'cleanup' the useEffect function...

You can find it under Realtime Database

Don’t worry it’s not something you need to have

yeah, I feel your pain lol

I would add those roles as any user extra information, in the firestore (another service firebase has). And link with a key each document with the corresponding user.

Kyle has a video about useRef. Basically, it's very similar to useState. But when the value store in useRef, the component will not re-render if the value has changed. And it's popular to use it to reference a HTML element.

I got the same error, I cloned the repo in the description and got the same error. It happens because in Login.js there is setLoading(false) which updates the component AFTER the history.push('/'). This updates the Login component after it is unmounted. I'm guessing Kyle probably forgot to delete it :P there is no need for it as when the component mounts again, the inital loading state is set to false again.

Hey guys, make sure you put 'email' as a parameter of the resetPassword(email) function within the AuthContext.js since we're passing in 'emailRef.current.value' as an argument within the ForgotPassword.js component. I also had this error and that was my issue which solved it.

@@eduardserei6859 it is needed if the login is failed, you have to set the loading to false

Someone solved it? Thanks

@@eduardserei6859 the same problem exists in the UpdateProfile. Remove setLoading(false) solved it

Did you find any solution ?

Likely forgot to add the AuthProvider in App.js

Same error. I couldn't find the solution.

same problem here

Hi! :) Have you found a solution for it? I'm also stuck at that part of the code, as I keep getting the same alert, although the passwords match

@@rtcodes4618 I think I did yeah, it's a pretty strange one. I figured it out today actually haha. You need at least 6 characters for your password to be successful. That's why you keep getting an error, even if the passwords match. Very strange and will see if I can add an message for this or find a solution.

Getting that too, is it because state is being set from the useEffect hook maybe?

I've read elsewhere that it might have to do with setLoading(false) in Login.js taking place AFTER the history.push('/') so I'm commenting that here for anyone in the future. Not sure though.

Same here, but I did the ubsubsrcibe thing.

same

same. how we can fix this?

It has to do with the Signup component. In the handleSubmit function, when you call the history.push() method your Signup component gets unmounted, and the one that your'e pushing to gets mounted. After unmounting, your'e trying to modify the state of the Signup component with the method setLoading, that's why you're getting the error. To solve it, you just have to set the loading state before using history.push() method

@@josevillar5508 wow great, it works !. Thank you very much friend!

@@DarwinAristaArevalo You're welcome! But tbh I was about to come back and fix my comment cause I thought I got it wrong... maybe it was not about the Signup component but the Login one... But anywayssss, I'm glad it helped

@@josevillar5508 may i know how to set the loading state? as in can i have a coding example? i'm quite new at this

@@josevillar5508 You’re a lifesaver. I spent 2 hrs. trying to fix this problem. I thought the onAuthStateChanged listener was not executing the unsubscribe call. Also, I was wrong about how a try/catch block works. I thought that the try/.catch block had an implicit return statement and that it stopped any further execution within the handleSubmit function. I didn't think the setLoading(false) would run. Putting the setLoading(false) inside the catch block fixed my problem. Thank you, José!