Widget is not refreshed when provider value changes

Question

I have a users Firestore collection where the ids are my users uid. When a user logs in (with Firebase auth), i'd like to wrap the whole application by the corresponding firestore document.

My code is the following:

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MultiProvider(
      providers: [
        StreamProvider(
          create: (context) => FirebaseFirestore.instance
              .collection('users')
              .doc(FirebaseAuth.instance.currentUser?.uid)
              .snapshots(),
          initialData: null,
        )
      ],
      child: MaterialApp(
        title: 'Flutter Demo',
        theme: ThemeData(
          colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
          useMaterial3: true,
        ),
        home: const AuthentificationWapper(),
      ),
    );
  }
}

class AuthentificationWapper extends StatefulWidget {
  const AuthentificationWapper({super.key});

  @override
  State<AuthentificationWapper> createState() => _AuthentificationWapperState();
}

class _AuthentificationWapperState extends State<AuthentificationWapper> {
  @override
  Widget build(BuildContext context) {
    var userList =
        Provider.of<DocumentSnapshot<Map<String, dynamic>>?>(context);

    var isLogged = userList?.data() != null;

    return Scaffold(
        appBar: AppBar(
          backgroundColor: Theme.of(context).colorScheme.inversePrimary,
          title: Text('test'),
        ),
        body: Center(
          child: isLogged ? Text('YOU ARE LOGGED') : LogginAccount(),
        ));
  }
}

The problem is when the user logs in, AuthentificationWapper is not being updated (the log in form is still being displayed). I need to make a hot reload in order to see the text YOU ARE LOGGED

Check out Check current auth state section of the documentation on how to listen to the changes in authentication state. — Peter Koltai
– Peter Koltai, Commented Feb 8 at 19:26
Currently your code uses the FirebaseAuth.instance.currentUser value at the time when MyApp is built that's why it works on hot reload. But it is not updated when the user is logged in or out. — Peter Koltai
– Peter Koltai, Commented Feb 8 at 19:31

Frank van Puffelen · Accepted Answer · 2025-02-08 19:54:17Z

2

As Peter commented, right now your code uses FirebaseAuth.instance.currentUser to determine the current user, which happens to be null when that code happens to run.

What you'll want to do instead is listen for the current user by listening for authStateChanges as shown in the documentation on getting the current user. The FirebaseAuth.instance.authStateChanges() in the sample code there gives you a Stream, so you can use another StreamBuilder or StreamProvider to also make the app respond to auth state changes.

answered Feb 8 at 19:54

Frank van Puffelen

603k85 gold badges895 silver badges868 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

woshitom Feb 9 at 8:06

I see, thank you, but i also want my firestore document to be a provider (i want to have access to this document everywhere in my app), how can i do so? do i need a provider inside a provider ? (the first provider would be the one listening to FirebaseAuth.instance.authStateChanges() and the second one would be the one listening to the firestore document ?

Frank van Puffelen Feb 9 at 15:52

I assume you'd need two separate providers: one for the user and one for the documents. I am no expert on providers, but a quick search shows some promising results: google.com/…

woshitom · Accepted Answer · 2025-02-09 17:36:21Z

Multiprovider widget did the trick

return MultiProvider(
      providers: [
        Provider<AuthentificationService>(
          create: (_) => AuthentificationService(FirebaseAuth.instance),
        ),
        StreamProvider<User?>(
          create: (context) =>
              context.read<AuthentificationService>().authStateChanges,
          initialData: null,
        ),
        StreamProvider<DocumentSnapshot?>(
          create: (context) {
            final authService = context.read<AuthentificationService>();
            return authService.authStateChanges.asyncMap((user) {
              if (user != null) {
                print('Creating Firestore stream for user: ${user.uid}');
                return FirebaseFirestore.instance
                    .collection('users')
                    .doc(user.uid)
                    .get();
              }
              print('No user logged in, returning null');
              return null;
            });
          },
          initialData: null,
        ),
      ],
      child: MaterialApp(
        title: 'Flutter Demo',
        theme: ThemeData(
          colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
          useMaterial3: true,
        ),
        home: const AuthentificationWapper(),
      ),
    );

Collectives™ on Stack Overflow

Widget is not refreshed when provider value changes

2 Answers 2

2 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related