How to handle StreamBuilder rebuilds resulting from navigation? about firebase_auth_demo_flutter

[bizz84]

@narciero thanks for mentioning this.

I have encountered this problem in various projects, however I haven't found a good solution yet.
One idea worth exploring is to convert the LandingPage into a StatefulWidget that holds a subscription to the onAuthStateChanged stream.

This way, a local FirebaseUser variable can be stored and updated when the user changes. And this may reduce unnecessary StreamBuilder rebuilds.

NOTE: I'm mentioning this as something worth exploring - I haven't tested it in practice.

[bizz84]

@narciero Take a look at the latest changes: #39.

With this setup, the auth state StreamBuilder has been moved above the MaterialApp, and I no longer see the rebuilds. I have tested that this works when pushing a new route, as well as showing the on-screen keyboard.

Closing - but let me know if you have more questions

[giorgio79]

Another solution mentioned here is using a Stateful widget https://stackoverflow.com/questions/56835372/flutter-stream-builder-triggered-when-navigator-pop-or-push-is-called