-
-
Notifications
You must be signed in to change notification settings - Fork 241
Error: Cannot reattach ActivatedRouteSnapshot with a different number of children #1830
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@NickIliev @tsonevn Any idea on this? |
same problem here, but I am using Angular 8.0
|
@jocafi Yes, unfortunately, there is no feedback from anyone. Hope this will be fixed in new Tab-View Redesign |
@vahidvdn Are you using router-outlet or page-router-outlet ? |
@lostation No, page-router-outlet doesn't handle it correctly. See here. |
Ok maybe it’s not related to type of router outlet in your case.
Anyway, considering my issue, I’ve just replaced router outlet by page router outlet in my TabView’s children and the issue was gone.
It has to be linked somehow… I also wonder if this issue could be related to a clearHistory = true … I will give a try.
Sorry to be to not very useful … I’m still discovering NativeScript…
Hope this bug will be fixed for TabView and its children’s routes of Nativescript v6 … wait and see.
L.
|
I'm not sure if it will be helpful but in my case, the solution to this error was to use the additional parameter skipLocationChange in options of navigate method. Eg.
|
Hi Guys, Any news on this? Got the same issue while navigating back: |
Same issue when using this.routerExtensions.back() with lazy-loaded tab routes |
The same issue. Any idea? |
@bpaczkowski-merix solution with skipLocationChange in the transition worked for me |
some issue here! |
while navigating back use extra option in this.routerExtension.back()
i hope it handles correctly this issue |
+1 for this issue. |
This worked for me. |
+1 for the issue. |
Any idea about it ? |
Guys, what is the solve of the problem / |
i dont can use bottomnavigation inside my application, because i can go to component Tabs and but i can return back to him from different component |
Here is my routing:
The scenario which leads to the error: First the app starts with tabs route, then I go to the login page, after that I go to register and then again I go to tabs page (and clean the history). After that if I go to login page again and get back to previous one (tabs page), the error occurs.
The error:
Any idea?
The text was updated successfully, but these errors were encountered: