How to properly delay a guard until angular knows the definitive session state

Angular 19

Hi, I have been playing around learning how to protect some routes with authentication

my problem is that the user state takes a moment to properly notify the final resolution

meaning that, if a user is authenticated and access to a protected route, the user state returns null and then the user, breaking the protection

I have been trying different techniques like BehaviorSubject and filtering the undefined state to know that firebase still didn't provide a final state

I have also found a guy getting the session from the cookies https://medium.com/@ignatovich.dm/securing-angular-applications-with-route-guards-and-firebase-auth-54c02bdd4811 it is sync and with a straight answer

if I could find some examples for these use cases I will appreciate !

ファイル、テスト、エントリーポイントは指定されていません。この issue では、Firebase 認証が解決するまで Angular route guards を遅延させる方法についてのガイダンスを求めています。まず、AngularFire API または例に期待される範囲を明確にし、その後、認証された route の再現可能な例をドキュメント化して、未解決の状態中にリダイレクトされないことを検証してください。

索引モデルが issue の本文から書いたものです。