You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I will explain a little bit about the Coordinator in the demo project. HomeTabCoordinator is a tab bar controller that contains 3 tabs: NewsCoordinator, MarketsCoordinator, UsersCoordinator. MarketsCoordinator is a page view controller that has 2 pages: StockMarketCoordinator and UTMarketCoordinator.
Can you help me identify where the problem is?
The text was updated successfully, but these errors were encountered:
This really depends on how you're using XCoodinator. I'd have to see how you're using XCoordinator to give you better advice, but my general solution to this is to wrap your ViewControllers in a wrapper object that conforms to Presentable then override this function in that that wrapper where the strongRouter is the Coordinator that presents that ViewController
basically when you transiton a ViewController despite UIViewController conforming to presentable, it itself is not a Router the coordinator that displays that ViewController is the Router so you have to point to that router in that function in order for deep linking to execute as expected.
now since you presented the module that knows about the router Deep linking should start working properly. This problem actually comes up again in other situations. This is my general workaround.
Thank you for the wonderful Coordinator library. I am having an issue related to deeplink chain.
The issue is that the deeplink only runs to the MarketsRoute route, while the StockMarketRoute does not execute.
I will explain a little bit about the Coordinator in the demo project. HomeTabCoordinator is a tab bar controller that contains 3 tabs: NewsCoordinator, MarketsCoordinator, UsersCoordinator. MarketsCoordinator is a page view controller that has 2 pages: StockMarketCoordinator and UTMarketCoordinator.
Can you help me identify where the problem is?
The text was updated successfully, but these errors were encountered: