Fixed
Status Update
No update yet.
Comments
jg...@google.com
Found the issue, ugh
Noticed that when I do the following:
transaction.addToBackStack(null)
When adding a Fragment with ViewPager2, the above issue occurs, although, idk if it's becaugh of gcFragments() anymore.
As soon as I un-comment that line, the issue disappears.
Noticed that when I do the following:
transaction.addToBackStack(null)
When adding a Fragment with ViewPager2, the above issue occurs, although, idk if it's becaugh of gcFragments() anymore.
As soon as I un-comment that line, the issue disappears.
jg...@google.com
Is the Sample application, to reproduce, move back really fast between page 2 -> 1 and vice versa (they are bottom buttons) a couple times.
Wait a couple seconds and page 1 (the black page) should turn white meaning the Fragment has been removed.
As soon as you comment line 40 on MainActivity, and attempt again, the error does not persist
Description
Version used: 1.0.0-beta01
Devices/Android versions reproduced on: Compilation
After upgrading, I quickly got the following erros on my CI :
After checking a bit which dependency include jacocoagent, I found two culprits (Navigation Component which I reported here
| \--- androidx.viewpager2:viewpager2:1.0.0-alpha06 -> 1.0.0-beta01
| +--- org.jacoco:org.jacoco.agent:0.8.3
| +--- androidx.annotation:annotation:1.1.0
| +--- androidx.fragment:fragment:1.1.0-rc01 -> 1.2.0-alpha01 (*)
| +--- androidx.recyclerview:recyclerview:1.1.0-beta01 (*)
| +--- androidx.core:core:1.1.0-rc01 -> 1.2.0-alpha02 (*)
| \--- androidx.collection:collection:1.1.0 (*)
Is that normal ? If it is, what can we do to avoid lint from failing ?