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
When node is stopped, it could still receive configuration changes. In that case, if transitionHandler is present, transitionAnimation would be triggered but, as UI is not there, will cause configuration to change but view wont exist.
How to solve:
Move globalActivationState to SLEEPING when node is stopped.
Check ActivityIntegrationPoint.
How to reproduce:
Create an activity with a rib tree that is a Parent with a button + 2 rib childs(RibA + RibB). RibA is default one.
In Container interactor bind some source( input,dependency...) to a configuration change use node.createDestroy{} scope.
From the parent button trigger a new activity, from that activity modify the source binded to configuration to push RibB.
Go back to initial activity.
Expected Behaviour: RibB is present.
Actual Behaviour: No rib is present.
The text was updated successfully, but these errors were encountered:
When node is stopped, it could still receive configuration changes. In that case, if transitionHandler is present, transitionAnimation would be triggered but, as UI is not there, will cause configuration to change but view wont exist.
How to solve:
Move globalActivationState to SLEEPING when node is stopped.
Check ActivityIntegrationPoint.
How to reproduce:
Expected Behaviour: RibB is present.
Actual Behaviour: No rib is present.
The text was updated successfully, but these errors were encountered: