Flutter Firebase & DDD Course [9] - Getting the Signed-In User

📗 Get the code 👇👇
github.com/Res...
📧 Get Flutter news 📰 and resources:
👉 flutter.education
👨‍💻 Do you write good code? Find out now!
resocoder.com/...
Build command: flutter pub run build_runner watch --delete-conflicting-outputs
We need to have a way to find out whether the user is already signed in or not and also to get the user's ID. We're going to get this data from FirebaseAuth and, of course, hide any mention of Firebase inside the domain layer.
Go to my website for more information, code examples, and articles:
● resocoder.com
Follow me on social media:
● / resocoder
● / resocoder
● / resocoder

[@amaromem1]

His code is so clean that can protect you from Covid 👌🏻

[@ResoCoder]

For sure 😂

[@JETLAI123]

​@@ResoCoder Nice to see your great tutorial again, please keep safe :) BTW don't forget to talk more about TDD video, it will give you double protection from COIVD hahaha

[@rizalhadiyansah]

Yay! Everytime you upload DDD tutorials, it feels like this is the best day in my life, thank you! 🎉❤

[@ResoCoder]

You're so welcome!

[@Brown-bk4ju]

@@ResoCoder Please since Firebase upgrade how to get current user using AuthFacade since _firebaseAuth.currentUser() no longer works

[@kondasri1418]

@@Brown-bk4ju @override Future getSignedInUser() async => optionOf(_firebaseAuth.currentUser?.toDomain()); try this

[@darias.398]

Man, i just wanted to thank you! We have this 4 week project in Uni to create an application. Our group had no idea how to develop an app. Your tutorials saved our project!

[@pasindunirmal]

For those following this after the firebase package update which replaced FirebaseUser with User and removed the currentUser() function here's a solution you can use @override Future getSignedInUser() async => optionOf(_firebaseAuth.currentUser?.toDomain()); extension FirebaseUserDomainX on User { CurrentUser toDomain() { return CurrentUser( id: UniqueId.fromUniqueString(uid), ); } } NOTE: I renamed our User class as CurrentUser. If you want you can also use named imports like import 'package:firebase_auth/firebase_auth.dart' as auth; extension FirebaseUserDomainX on auth.User { User toDomain() { return User( id: UniqueId.fromUniqueString(uid), ); } }

[@hecher78]

Thank you so much for your help!

[@DanielSanchezV]

Wonderful! Every time you upload a video I know there something new to learn! What about spending 10 seconds at the end of the video introducing what is going to be next? So that attendees like me can try to achieve the result by themselves and see your solution at the end. It's a good way to learn faster and better. Let me know! :)

[@sumosnow]

I'm not sure where the VS Code 'vobj' snippet for Value Objects is published online, so here it is in case of use: "Value Object": { "prefix": "vobj", "body": [ "class ${1} extends ValueObject {", " @override", " final Either value;", " factory ${1}(${2} input) {", " return ${1}._(", " // insert validation", " );", " }", " const ${1}._(this.value);", "}" ], "description": "Value Object" },

[@lowlydeveloper3693]

Thanks!

[@albanr8028]

Thanks

[@kelroar]

Please update the repo. This series is so good you cant let it die like this please. It is really helpful content. 😥

[@haidarrmehsen]

Here is a Like before watching the video :)

[@dalestewart]

Fantastic tutorial. Your code is so logical and clean. True professional Flutter developer. Thanks

[@msilvamolina]

Awesome 👏 👏 👏 Thanks you for this content. I have a little question... what's is the icon theme for vscode you use?

[@h3w45]

in firebase_user_mapper file the code has been changed to this import 'package:firebase_auth/firebase_auth.dart' as firebase; extension FirebaseUserDomainX on firebase.User {} also to get the current user inside firebase_auth_facade file @override Future getSignedInUser() async => optionOf(_firebaseAuth.currentUser?.toDomain());

[@prajwalsbelagavi6896]

Thank you for the tutorial. Much awaited !

[@asimabdalla3344]

Hit Matt Can you provide us with the value Objects Snippets pls

[@tutorialnacional]

Great tutorial series, keep it up!

[@rshrewd8809]

Awesome awesome awesome awesome 👍👏

[@mikemannox4191]

What is `import 'package:notes_firebase_ddd_course/domain/core/errors.dart';` used for at 17:51?

[@THEMithrandir09]

What's the difference between using Future< T, Unit> vs. Just using Option?

[@mdazharuddin4684]

I think you mean Either vs Option

[@0877adri]

Oh no i watched it till the end. I finally understand why people wait till the whole season is out.

[@heduinravell4785]

I needed to add to main.dart: await Firebase.initializeApp(); just above runApp(AppWidget());

[@IAmTheMainCharacter]

reso ddd seems kinda long and only for big project not for medium. It it worth it for small apps?

[@ResoCoder]

Nope, it's only worth for HUGE apps, if even that. Many concepts are applicable to small apps too but I'd rather not implement value objects at all.

[@1b0o0]

I strongly recommend you to read this short book on the topic. It's pretty straight forward and easy to understand. learning.oreilly.com/library/view/what-is-domain-driven/9781492057802/

[@mitchross2852]

@resoWhat tutorial series would you recommend for small-medium apps that need to manage auth ?

[@patrickkarlsson812]

@@ResoCoder Just out of curiosity, how would you do instead of implementing value objects? If you would code a real flutter project, do you mean that you should not go for a non-representable state via value objects and instead just validate in the presentation layer? What architecture are you using in your real projects? Great youtube content by the way :)

[@urklegizmo]

​ @Reso Coder I would also like to know your thoughts on Patricks question

[@xerzes5900]

The Long Wait Begins

[@heduinravell4785]

Firebase changed FirebaseUser to User, now there is a conflict with internal class User. I had to import 'package:[...]/domain/auth/user.dart' as user; then I used user.User for internal User.. and User for firebase

[@AntonDerevyanko]

Remember: restart is the best solution in your life :))))

[@mqhamdam]

Is class User from FirebaseAuth or from the domain layer?

[@Flutterdev6391]

I just want to ask one thing that am I only who understand clearly these series after watching 2-3 times ?

[@ResoCoder]

You're quite a fast learner actually. I was reading articles about general DDD 5 times in a row at times to grasp the concepts.

[@Flutterdev6391]

@@ResoCoder thanks matt it's give me a lot of confidence😊

[@pasindunirmal]

For those looking for 'vobj' snippet add this to user Snippets dart.json file "Value Object Class": { "prefix": "vobj", "body": [ "class ${1} extends ValueObject {", " @override", " final Either value;", "", " factory ${1}(${2} input) {", " return ${1}._(", " //insert validation", " );", " }", "", " const ${1}._(this.value);", "}" ], "description": "Create a Value Object Class" },

[@wawrzyn3059]

thanks!

[@lowlydeveloper3693]

Unfortunately, there are major breaking changes starting with firebase_auth 0.18.0 ... currentUser() method, was replaced with the property currentUser, and it no longer returns a Future. So our method getSignedInUser() will no longer work as written... Does anybody have any ideas how to fix this? Or @Reso Coder would you please update the github repository for the project? Much appreciated! Here's more background info: stackoverflow.com/questions/63482162/undefined-class-firebaseuser

[@lowlydeveloper3693]

I thought about it, and here's one way to get it working. However, I am new at this. So if there is a more elegant way, please let me know. 🙂 Also note that 'FirebaseUser' type is now gone and replaced with 'User', so we have a name clash with our app 'User' definition. To circumvent it, I used import 'package:firebase_auth/firebase_auth.dart' as fb; Option _maybeUser(String uid) { return (uid == null || uid == '') ? const None() : Some(User( id: UniqueId.fromUniqueString(uid), )); } @override Future getSignedInUser() { final fbUid = fb.FirebaseAuth.instance.currentUser.uid; return Future.value(_maybeUser(fbUid)); }

[@lowlydeveloper3693]

Oops, there is a bug above in _getSignedInUser()_ ...I missed the question mark (short-circuit operator) to account for _null_. It should be like so: final fbUid = *fb.FirebaseAuth.instance.currentUser?.uid*

[@AdamSmaka]

@@lowlydeveloper3693 Seems good to me, thanks a lot!

[@iracemamobile8964]

The resocoder's github project is not updated.

[@binaerverkehr]

Why don't you use the built-in class "UniqueKey"?

[@lowlydeveloper3693]

The description on the `currentUser` getter says this: `You should not use this getter to determine the users current state, instead use [authStateChanges], [idTokenChanges] or [userChanges] to subscribe to updates.` I am not clear why it would be a problem to use the `currentUser` as the proxy for the state of signed in user, however, it appears that this code needs to be updated to reflect the current version of FirebaseAuth. Anybody knows, or has any suggestions?

[@lowlydeveloper3693]

Here is one idea I thought about using FirebaseAuth recommended [authStateChanges] method (I'm using firebase_auth: ^1.2.0). This should allow us to monitor user authentication state. However, I have not tested it yet to verify that the solution works or not: // In domain layer, IAuthFacade: Stream getSignedInUser(); // Infrastructure implementation in FirebaseAuthFacade: @override Stream getSignedInUser() async* { final userStateStream = _firebaseAuth.authStateChanges(); await for (final user in userStateStream) { yield optionOf(user?.toDomain()); } }

[@vaibhavdangayachvd]

What if we add some more providers then the size of this file would become large. Any way to tackle this? And also when we use verifyPhoneNumber method of firebase it expects some callbacks so how can we express this in a clean way? What I did was that i provided some handler function like handel-failure and handel-success and set the return type to void...is this correct? A verification id is generated when otp is sent should be stored in bloc or in the facade implementation itself?

[@APEDUCO]

it depends. if you are using verificationId variable in if checks than you should store it in IAuthFacede interface and override it in auth facade in Infrastructure layer. but it would be better keeping in the infrastructure layer and if checking the verification id and returning either AuthFailure or FirebaseUser or unit as matt describes. although keeping it in the infrastructure layer will also help in manually signing in the user using OTP when auto retrieval callback fails in verify phone number method. hope this helps 👍👍

[@APEDUCO]

phone verification is slightly different than other signing in methods. there are 3 possible outcomes or states ("failed" , "otp not automatically retrieved", "signed in user"). allow user to enter phone number then navigate them so they can enter the received OTP and than manually sign them up using Phone Auth Provider.

[@arifikhsanudin9724]

Can i separate auth and notes in features folder like in tdd?

[@Brown-bk4ju]

Please since Firebase upgrade does anyone know how to get current user using AuthFacade?

[@adriano_souza]

did you get it?

[@LjaDj5XQKey9mSDxh4]

I can't find the extension for the snippets 'fdatac' and 'ptf' :/

[@Brown-bk4ju]

its a code snippet he created and added to dart.json in VS Code

[@iqboladahamjonov9835]

I would recomment not to call User the class which is defined in damain auth folder, because dart will confuse it the User class which is defined in Firebase auth package.

[@NimoArts]

I would recommend using import '...' as ...; so you are not forced to rename User class just because firebase_auth(or any other dependency) has a User class as well

[@arifikhsanudin9724]

where is the snippet vobj?

[@mahmudulhasan4979]

in firebase 1.4.1 this code Future getSignedInUser() async => optionOf(_firebaseAuth.currentUser!.toDomain()); said that can The argument type 'User' can't be assigned to the parameter type 'User?' how can solve this any one have any clue??

[@biplabdutta]

_firebaseAuth.currentUser?.toDomain()

[@mahmudulhasan4979]

@@biplabdutta thanks but currentUser data type is User? so toDomain() is not assigned with currentUser because toDomain() data type is User. that's why ist saying type 'User' can't be assigned to the parameter type 'User?'

[@mahmudulhasan4979]

@Flutter optionOf(_firebaseAuth.currentUser?.toDomain());

[@AdamSmaka]

After updating firebase to newer version the code needs to be updated too. This is how I handled it, correct me if it's wrong. import 'package:firebase_auth/firebase_auth.dart' as firebase; @override Future getSignedInUser() { return Future.value(optionOf(_firebaseAuth.currentUser?.toDomain())); } __ import 'package:firebase_auth/firebase_auth.dart' as firebase; ... extension UserDomainX on firebase.User { User toDomain() { return User(id: UniqueId.fromUniqueString(uid)); } }

[@abdoselim1990]

firebase documentation tells u specifically not to do that : [currentUser] "Returns the current [User] if they are currently signed-in, or `null` if" "You should not use this getter to determine the users current state," "instead use [authStateChanges], [idTokenChanges] or [userChanges] to" "subscribe to updates." i hope that clears it up a bit, if u get to a solution let me know. im stuck here as well

[@AdeYudysTriawan]

hai matt, i have a question..if i fetch data from api which is not supported real time update like firebase, do i need use stream type like u do with notes in finished project or just future? thanks

[@APEDUCO]

use Future instead for non realtime database services. You can call the fetching function periodically or onRefresh callbacks to mimic the realtime sort of thing kind of 🤞.

[@vaibhavdangayachvd]

@@APEDUCO I think we can use streams and in on-refresh we can send loaded data as stream

[@APEDUCO]

@@vaibhavdangayachvd you can use streams that way and always remember to update the data whenever a change occurs. 👍 you can take a look at ticker example in the bloclibrary.dev/#/fluttertimertutorial

[@parthpatel9757]

Anyone find vobj snippet?

[@ilg8410]

25:00

[@jeromestsauver]

I always see 1 downvote on each of these - same person? lol