IssueTracker

When using the new state manager released in fragment 1.3.0-alpha08, if you manually (without using the hide/show fragment transactions) set the visibility state of your view after the SpecialEffectsController has started any animations/transitions on your view, the visibility changes are ignored.

The reason this happens is because the new state manager saves the visibility state of the view in onViewCreated() as the final state and then restores that visibility state once the special effect completes after onStart(). This means that any changes made by the user to the view visibility state between onViewCreate() and onStart() are completely ignored.

This becomes apparent in two particular cases:

1. There is a fragment that is always added, but has its visibility state updated based on some internal data (i.e. an error screen that is set to View.INVISIBLE when there is no error and View.VISIBLE when there is one). If the view state changes to INVISIBLE in onStart(), the fragment should not be shown once the add transaction completes.

2. A entering fragment is postponed and while it is postponed, its view visibility state is set to View.INVISIBLE. Even once the fragment is no longer postponed, its view should still be INVISIBLE until the user changes it again manually.

The new state manager should defer view visibility state control to the user no matter when the state is changed. Doing so would ensure that the user always has the source of truth for their Fragment's view visibility.