Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Attachment actions
Unintended behavior
View staffing
Description
Version used: Both 1.3.5 and 1.4.0-alpha04 with new state manager enabled. + Transition lib 1.4.1
Devices/Android versions reproduced on: Pixel 3 API 28 emulator
The code here seems to cause the issue:
In the error scenario, the fragmentView is set to GONE, but is also included in the exitingViews list so is immediately set back to VISIBLE:
fragmentView.setVisibility(View.GONE);
final int numViews = exitingViews.size();
for (int i = 0; i < numViews; i++) {
exitingViews.get(i).setVisibility(View.VISIBLE);
}
I have attached a screen recording and a test app project. To see the issue, just launch the app and click hide. It will only work once, so if you want to reproduce again you'll have to back out and launch again.