Results
1
comments of
Chanaka
same issue occurred in angular 18.2.5 with **CanActivateChild**. but after more research i never found good solution. finally i use **CanActivate Guard** for each of router child objects. now it...