We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When I'm giving control to multiple flows using a tabBar, after Flows.use, I have something like following (I tried both ExecuteStrategy's.):
ExecuteStrategy
return .multiple(flowContributors: [ .contribute( withNextPresentable: tab1Flow, withNextStepper: OneStepper( withSingleStep: Tab1Step.needsTab1 ) ), .contribute( withNextPresentable: tab2Flow, withNextStepper: OneStepper( withSingleStep: Tab2Step.needsTab2 ) ), .contribute( withNextPresentable: tab3Flow,, withNextStepper: OneStepper( withSingleStep: Tab3Step.needsTab3 ) ), .forwardToCurrentFlow(withStep: TabBarStep.tabBarIsReady) ])
In this case, I cannot register steps in sub flows. It only registers the initial steps I give in OneStepper but after that no steps are registered.
Everything works fine if I remove .forwardToCurrentFlow(withStep: TabBarStep.tabBarIsReady) from contributors.
.forwardToCurrentFlow(withStep: TabBarStep.tabBarIsReady)
As a thought, this might be related to #175
The text was updated successfully, but these errors were encountered:
Looks like resolved in 2.12.4 with #175
2.12.4
Sorry, something went wrong.
No branches or pull requests
When I'm giving control to multiple flows using a tabBar, after Flows.use, I have something like following (I tried both
ExecuteStrategy
's.):In this case, I cannot register steps in sub flows. It only registers the initial steps I give in OneStepper but after that no steps are registered.
Everything works fine if I remove
.forwardToCurrentFlow(withStep: TabBarStep.tabBarIsReady)
from contributors.As a thought, this might be related to #175
The text was updated successfully, but these errors were encountered: