Peter Friese

Just a few remarks: 1. Can we rename the title of the PR to something more descriptive? I think it's OK to mention this is a re-implementation of an existing...

Hi @jesus-mg-ios - that's right, you need to monitor the authorisation state yourself. This is because the user might be authenticated using more than just one provider (e.g. Sign in...

Hi @linkillhz - you can delete user accounts in Firebase Auth using `user.delete()`: ```swift if let user = Auth.auth().currentUser { do { try await user.delete() } catch { print(error) }...

Hi all - Thanks for raising this issue - we are aware of this and are actively working on a solution. We will update this issue once we can share...

Hi all, We are working on a long-term solution that will call Apple's REST API for token revocation when you delete a Firebase user account that was created using Sign...

Thanks for creating the code generator, @jooyoungho - this looks like a useful resource! Regarding `UserDefaults` - I think it would be useful to call this out more prominently in...

If you can use async/await in your app, you can call this method asynchronously: ```swift func refreshIDToken() { Task { do { idToken = try await user?.idTokenForcingRefresh(true) ?? "" }...

@LilaQ my suggestion was, can you get rid of semaphores and replace them with async/await? ```swift Task { do { idToken = try await user?.idTokenForcingRefresh(true) ?? "" makeCallThatRequiresIDToken(idToken) } catch...

Understood. I suggested this approach as it is available now, and we expect async/await to see more adoption going forward.

Let me look into the lint checks. I was thinking about renaming the block parameter to `completion` as well at first, but was worried that this would be a breaking...