A sample Android app that demonstrates how to use Firebase Authentication, Crashlytics, Cloud Firestore and Hilt with Jetpack Compose UI

There is a subtle bug making tasks map store inconsistent data

Reproduce

• Make sure you are not logged in
• Create a task
• Login to an existing account
• Going back to the tasks page, the task created on step two will be there (ViewModel was persisted). Now you won't be to edit it because it is no longer linked to your account.

Why: Logic to update userId during the login process was removed #18

Fix: Clear tasks when removing the storage listener on the tasks ViewModel

Hi there, thanks for creating the project to nudge the community towards the recommended way to work with Firebase.

I just have one suggestion for now which is to do a state hoisting on the screen — I've submitted one example and can do the same for the other ones if you guys are happy with it —.

After doing the state hoisting we can add the preview tag to the screen and enable live edits — when using Android Studio Electric Eel — to have fast feedback on UI changes.

Please feel free to discard the PR if you feel it is not useful.

Hey @marinacoelho!

First, thanks for putting together your series of articles about getting started with Firebase and Compose. It was the perfect series I found to get started on a side project I'm working on.

I found a potential bug when implementing the firebase authentication. When creating an account I was getting an error stating the account was already linked to the given provider. This was happening because we were creating the account and then trying to link it to an existing (anonymous) account. But after creating the account we lost the anonymous account credentials and Firebase.auth.currentUser was pointing to the new authentication provider (email in this case).

The fix was to not create the account and instead "promote" it to the email provider account.

Something similar happens when the user signs in. Since the account is already created, Firebase cannot link an anonymous account with an existing one, and you cannot "promote" an already promoted account. The best we can do is to copy the data the anonymous account had, over to the logged-in account. I removed the linkWithEmail step because it will fail. Another thing that we can add to it is to delete the anonymous account after signing in to avoid cluttering the user database with anonymous accounts (altho we can activate the auto-cleanup to remove the anonymous account 30-days old.

If you think this is correct, it'll be great if the piece of Part 2 of your series clarifies this.

Upon returning from a successful login or account creation, we proceed to the next step, which is to get the credentials the user used to sign in to the second authentication provider, and link them to the anonymous account

I hope this helps and makes sense.

Thank you again 🙏

I've noticed how this app is using UUID.randomUUID().toString() to generate a document ID and save it on Firestore: https://github.com/FirebaseExtended/make-it-so-android/blob/40e46da8b587f0466e08a051a41d67c7088083f2/app/src/main/java/com/example/makeitso/model/service/impl/StorageServiceImpl.kt#L69-L73

It would be nice to demonstrate Firestore's auto-generated ids instead:

 Firebase.firestore 
     .collection(TASK_COLLECTION) 
     .add(task) 
     .addOnCompleteListener { onResult(it.exception) } 

And when reading the tasks, we'd manually set the id:

value?.documentChanges?.forEach {
    val wasDocumentDeleted = it.type == REMOVED
    val task = it.document.toObject<Task>().apply { task.id = it.document.id  }
    onDocumentEvent(wasDocumentDeleted, task)
}

Hi there, thanks for creating the project to nudge the community towards the recommended way to work with Firebase. I just had one suggestion for now which is to do a state hoisting on the screen — I've submitted one example and can do the same for the other ones if you guys are happy with it —.

After doing the state hoisting we can add the preview tag to the screen and enable live edits — when using Android Studio Electric Eel — to have fast feedback on UI changes.

Please feel free to discard the PR if you feel it is not useful.

Hi there, thanks for creating the project to nudge the community towards the recommended way to work with Firebase.

I just had one suggestion for now which is to do a state hoisting on the screen — I've submitted one example and can do the same for the other ones if you guys are happy with it —.

After doing the state hoisting we can add the preview tag to the screen and enable live edits — when using Android Studio Electric Eel — to have fast feedback on UI changes.

Please feel free to discard the PR if you feel it is not useful.

Could you tell me, please, in simple words, what does the line mean? viewModelScope.launch(showErrorExceptionHandler)

1. In which Dispatcher does the coroutine run?
2. How to run in Dispatchers.IO or do I need to add withContext(Dispatchers.IO) later?

This pull request updates the project to use the most recent versions of all libraries, sdks and Gradle. From now on, this project can only be opened using Android Studio Chipmunk+. This pull request also adds Remote Config, used to show/hide the edit option for each task item, and Performance Monitoring, used to add custom traces and measure some service methods.

Updated composable functions parameters to match the most recent recommendations by the Compose team. Algo updated .gitignore to ignore google-services json file.

An old Snackbar message gets displayed when launching the app from the recent list

Steps to reproduce

• Open the app, and do anything to trigger Snackbar message i.e. invalid login
• Close the app by clicking the back button
• Reopen the app from the recent app list
• Snackbar message will be displayed