Weak-password | dictionary - | Dictionary library

Your authListener() in Login.js is setting a state variable in the Login component, but it does not communicate the change of state back to the rest of the application.

One way to resolve this would be to move the const [user, setUser] = useState() from Login.js to Home.js, then pass setUser as a prop to . That way, when the onAuthStateChanged() gets the user object, you set it in state at the Home level.

You'd additionally change the condition statement in Home.js to be:

try on catch blocks work like this.

try executes code. If that fails, it throws an Exception.

Now, that Exception can be of many types and using on and catch together we can catch a specific exception and get that value inside e.

But the on FirebaseAuthException catch (e), only catches Exceptions of type FirebaseAuthException.

So, in a case where your try block throws something else, maybe NumberException, then it won't be caught.

For catching all other types of Exceptions, you need to add another catch block.

Like this,

You can find the possible errors in the documentation for the Flutter firebase_auth package.

For instance, the createUserWithEmailAndPassword method has the following possible errors:

• email-already-in-use: Thrown if there already exists an account with the given email address.

• invalid-email: Thrown if the email address is not valid.

• operation-not-allowed: Thrown if email/password accounts are not enabled. Enable email/password accounts in the Firebase Console,
  under the Auth tab.

• weak-password: Thrown if the password is not strong enough.

It's the same for the other methods that throw errors.

Since you do this:

I am seeing your handleLogout function has typo?

Your code

To detect if an email is already in use, don't call createUserWithEmailAndPassword, but instead call fetchSignInMethodsForEmail .

You can copy paste run full code below
You can use ScaffoldMessenger, you can change from

This issue is because your login component is loading directly without any props. You should load the login component through the App component to get all the props.

For that make the below changes in routes.js,

Your return value has to be of the type declared with the Future's generic type. If there are any code paths that don't return a UserCredential, then you can't use this declaration. If you have no return value, then yes, it should be Future. But it seems that you do have a return value in at least one code path.

Consider instead moving all of the UI code out of this method and simply let the function throw whatever it throws (or re-throw something else). Then, make the caller of this function catch the error and decide what to show in the UI for that case.