The need to recover gracefully from iOS Obj C view controller navigation error

[NathanWalker]

I wanted to track this here since it is more problematic with the Angular integrations with NativeScript. This can happen under all sorts of conditions that the user/developer has no control over. Could be some asynchronous handling when attempts were made to navigate but no longer can or a data resolver firing at an unexpected time and/or under other unexpected conditions which were intended to result in navigation of the app.

pushViewController:animated: called on <UINavigationControllerImpl 0x7ff37abf7a00> while an existing transition or presentation is occurring; the navigation stack will not be updated.

In all cases, NativeScript for Angular should handle this gracefully. Right now, when this occurs, it leaves the app completely unable to navigate further. Doesn't crash the app but might as well since the app is completely unusable after this occurs. Likely angular router updates but yet the underlying native navigation did not leaving the app in a very unstable condition.

[exeleon]

Hi @NathanWalker
Which is the NativeScript team point of view about this?. We are experimenting the same issue in our project.

[salvadorcoronel]

Hi @NathanWalker,
I have the same problem in my app,
What alternative did you apply to solve the problem?
I understand that this is still in the NS Team backlog.

[salvadorcoronel]

Hi @NathanWalker

Here the log from xCode

2019-09-11 10:18:44.303179-0500 nameProject[43499:13249068] setViewControllers:animated: called on <UINavigationControllerImpl 0x7f9716844e00> **while an existing transition or presentation is occurring; the navigation stack will not be updated.**