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
It reapears after going to the main menu and back to solo.
Probably qosmetics activates another FlowCoordinator which then calls PresentFlowCoordinator and disables the Button. But because we go back instead of (newly) presenting the Solo Controller, PresentFlowCoordinator is not being called (and the Button stays deactivated).
Maybe it is enough to hook FlowCoordinator.DidActivate instead of PresentFlowCoordinator
The text was updated successfully, but these errors were encountered:
It reapears after going to the main menu and back to solo.
Probably qosmetics activates another FlowCoordinator which then calls PresentFlowCoordinator and disables the Button. But because we go back instead of (newly) presenting the Solo Controller, PresentFlowCoordinator is not being called (and the Button stays deactivated).
Maybe it is enough to hook FlowCoordinator.DidActivate instead of PresentFlowCoordinator
The text was updated successfully, but these errors were encountered: