Skip to content

new firebase_auth 0.18 beaking changes #10

Description

@AbdoZDGaia

as of update 0.18 there's been changes in the way user state is handled.
_firebaseAuth.CurrentUser() is no longer usable, CurrentUser is now just a getter.

/// Returns the current [User] if they are currently signed-in, or null if /// not. /// /// You should not use this getter to determine the users current state, /// instead use [authStateChanges], [idTokenChanges] or [userChanges] to /// subscribe to updates.

can you please, even if you're not willing to update the entire project, just tell me how to handle the "authStateChanges" stream
for example through the firebase authentication facade? and pass it down to states and firing events based on how we listen to it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions