[BottomNavigation][Tabs][Android] Outlet becomes unresponsive/freezes when using nested outlets

[paul-staskiewicz]

Which platform(s) does your issue occur on?

• Android

Please, provide the following version numbers that your issue occurs with:

• CLI: 8.5.3
• Cross-platform modules: 8.5.2
• @nativescript/android: 8.5.0
• Plugin(s): @nativescript-community/ui-material-bottom-navigation > 7.0.0

Please, tell us how to recreate the issue in as much detail as possible.

When I navigate forward in a tab/parent outlet and then switch to a second tab and reset the outlet in the first tab, the outlet becomes unresponsive and i can not navigate to other routes in this outlet. This issue is only present on Android. Only versions >7.0.0 are affected. This behavior/issue was introduced with release 7.0.1: https://github.com/nativescript-community/ui-material-components/releases/tag/v7.0.1. When downgrading to 7.0.0 it works fine.

Is there any code involved?

I have created an example showcasing the problem: https://github.com/paul-staskiewicz/ns-frozen-outlet. There are two tabs (list/process) with each containing a page-router-outlet. The process tab has three child routes which represent a process, in which you are navigated from step1 -> step2 -> step3 -> list (switch to list tab). When switching back from the list tab to the process tab, it is not possible to go further than step1.

[paul-staskiewicz]

I have did some digging, and the root cause of this problem is this pull request: #405.

When fixing @nativescript-community/ui-material-core-tabs to version 7.0.27, the issue disappears.

[farfromrefug]

@edusperoni any chance you could look at this?

[edusperoni]

I'll try to investigate it soon. It's a bit weird because that PR actually fixed some other Frame freezing issues (freezing when switching to currentTabIndex + or - 2)

[pap5508]

I am facing similar issues on iOS as well. after receiving push notifications and navigating nested outlets blocks further navigation to the previous screen.

[jessorlisa]

@paul-staskiewicz @farfromrefug @edusperoni Has this ever been solved?

[paul-staskiewicz]

@paul-staskiewicz @farfromrefug @edusperoni Has this ever been solved?

The last time I've tried (a month ago with the most recent versions) it was still an issue.

[jessorlisa]

Thx @paul-staskiewicz for the confirmation. I think I ran into the same situation. Hopefully this will be addressed soon. What's your current workaround? Sticking to @nativescript-community/[email protected]?

[paul-staskiewicz]

Thx @paul-staskiewicz for the confirmation. I think I ran into the same situation. Hopefully this will be addressed soon. What's your current workaround? Sticking to @nativescript-community/[email protected]?

We are currently fixing the version of @nativescript-community/ui-material-core-tabs to 7.0.23. That is the last working version for us.

I have did some digging, and the root cause of this problem is this pull request: #405.

When fixing @nativescript-community/ui-material-core-tabs to version 7.0.27, the issue disappears.

So this may be wrong. It could be that the issue was introduced with https://github.com/nativescript-community/ui-material-components/commit/23b25b9055faddee4a2cb73f977d60f76145aadf. It has been some time that I looked into it.