Fixed
Status Update
No update yet.
Comments
t....@gmail.com
I can guarantee that onCreateView() is indeed being called twice, and there is an onDestroyView() in between. So there may be an issue with your tests.
Were you not able to reproduce the problem with a BottomNavigationView and a call to startPostponedTransition()?
Were you not able to reproduce the problem with a BottomNavigationView and a call to startPostponedTransition()?
il...@google.com
Thanks, we could reproduce the bug after some time.
A pending fix is athttps://review.source.android.com/24433
A pending fix is at
t....@gmail.com
Fix submitted to AOSP tree.
il...@google.com
I see same problem with ubuntu 11.04 natty fresh install, as it was fresh i loaded sdk r12, with sun java 6 u26.
t....@gmail.com
Is there a workaround available till SDK R13 besides running at scale < 0.5 or >= 1.0?
si...@gmail.com
I also am seeing this problem with Ubuntu 11.04 and SDK 12.
il...@google.com
I'm also seeing this issue with LinuxMint 11 LXDE.
t....@gmail.com
Sorry for the inconvenience, where is file argb.h
sm...@gmail.com
any workaround till r13 ?
il...@google.com
Same here with Ubuntu 11.04 (64 bits) and SDK 13...
The link given above to get the fix doesn't work for me :(
The link given above to get the fix doesn't work for me :(
Description
Version used:
androidx.navigation:navigation-fragment-ktx:2.2.0-rc01
androidx.navigation:navigation-ui-ktx:2.2.0-rc01
Devices/Android versions reproduced on:
Pixel 3
Android 10
When switching tabs (using BottomNavigation / setupWithNavController()), when the destination Fragment contains a call to postponeEnterTransition() in onCreate() or onCreateView(), the onCreateView() lifecycle method gets called twice. This behavior is visible to the user, via a sort of 'flicker' (depending on the layout), as the fragment's view is recreated.
I suspect this may be due to some code in
`FragmentManager.addAddedFragments(@NonNull ArraySet<Fragment> added)`
It appears the destination Fragment (which invoked postponeEnterTransition()) has moveToState() called on it twice (vie addAddedFragments()). My guess, is that the destination fragment hasn't completed its first moveToState() before the second moveToState() is called, so the secondMoveToState() is attempting to move from a stale state.
I'm not able to provide a sample project for you at this stage.