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 !

No se nombra ningún archivo, prueba ni punto de entrada; el issue solicita orientación sobre cómo retrasar Angular route guards hasta que se resuelva la autenticación de Firebase. Primero aclara el alcance esperado de la API o del ejemplo de AngularFire; después documenta un ejemplo reproducible de una ruta autenticada y verifica que no redirija durante el estado no resuelto.

Escrito por el modelo de indexación a partir del texto del issue.