Hi everyone, Apologies beforehand if I can't provide any good examples/failed tests/reproducible steps, I am struggling to find the code that causes the problem in the first place.
This is my setup: - Angular 2: 2.4.6 - Firebase: 3.6.8 - AngularFire: 2.0.0-beta.7 Running a multi-tenant app (multiple teams groups that can be switched from one another). Large codebase. Steps to reproduce the problem: - Authenticate with the app for the first time (via Firebase Javascript authentication API). - On the first session, I navigate through the app fine until I reach a screen to add a new item. - When I click on "add item" (from a 3 levels deep child component), Angular recognises a Route and redirects me to a top level route (`/:team-name/elements`). This shouldn't be happening. - If I navigate back to that same screen and try adding new items again, the undesired navigation clears away and items get created and stacked nicely where they belong. Weirdness: - There are no explicit `navigate()` calls in the whole app. Certainly not after the `update()` call in our `items.service` which generates an API call to the Firebase database. - I can reproduce the bug if I log out and log in back again, but works well after that initial session request. Challenges: - Enabling the tracing options for our routes only gives me information that the navigations are being resolved, but I can't detect which file is calling the `navigate()`. - I'm still not sure if the issue is in Angular, Firebase or AngularFire. Any leads that can allow me to at least reproduce the issue in a plunkr/jsbin environment would be much appreciated. -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
