IssueTracker

Project: platform/frameworks/support
Branch: androidx-main

commit a735aaa4d06c90454de772fae5a02f6cbde210b3
Author: Jeremy Woods <jbwoods@google.com>
Date:   Tue Feb 28 22:58:23 2023

    Ensure FragmentNavigator destroys intermediate entries on popUpTo
   
    We need to make sure that when Fragment are destroyed their entries are
    also always destroyed.
   
    RelNote: "Fixes a regressions in previous release that caused the wrong
    BottomNav menu item to be highlighted when using system back to go
    between tabs."
    Test: Added FragmentNavigatorTest
    Bug: 270447657
   
    Change-Id: I634f6047b7016bcb8b690047605a6f66b2dc1438

M       navigation/navigation-fragment/src/androidTest/java/androidx/navigation/fragment/FragmentNavigatorTest.kt
M       navigation/navigation-fragment/src/main/java/androidx/navigation/fragment/FragmentNavigator.kt

https://android-review.googlesource.com/2461556

Project: platform/frameworks/support
Branch: androidx-main

commit 96cee05bdb8f61a92e4be00a52b991cfc1ed2f4e
Author: Clara Fok <clarafok@google.com>
Date:   Wed Mar 01 12:28:09 2023

    Add FragmentNavigator test to assert entry destroyed
   
    Add test to assert that NavBackStackEntry is destroyed after being restored upon recreation/configuration change.
   
    Asserts that the fix on this bug also fixes b/270610768.
   
    Test: ./gradlew navigation:navigation-fragment
    Bug: 270447657
    Change-Id: I8874d2dfaa17e560dd2f6d9da54e435494c187d2

M       navigation/navigation-fragment/src/androidTest/java/androidx/navigation/fragment/FragmentNavigatorTest.kt

https://android-review.googlesource.com/2464422

Project: platform/frameworks/support
Branch: androidx-main

commit 7cf55857f0db6bd1a1e1f95be7374ed5cf3eca58
Author: Jeremy Woods <jbwoods@google.com>
Date:   Wed Mar 15 16:59:50 2023

    Fix system back after popUpTo
   
    After you do a popUpTo inclusive while using Navigation with Fragments,
    if you attempt to do a system back call, the Navigation back stack is
    never updated.
   
    The reason for this is that when fragment views are DESTROYED, we need
    for the observer in the FragmentNavigator to update the state so we know
    that the entry was already popped.
   
    RelNote: "When using system back after doing a navigate with popUpTo,
    the state of the NavController will pop to the correct entry."
    Test: Added OnBackPressedTest
    Bug: 270447657
   
    Change-Id: I3a8ec072ba6d1655ab054cc081961825909088e6

M       navigation/navigation-fragment/src/androidTest/java/androidx/navigation/fragment/OnBackPressedTest.kt
M       navigation/navigation-fragment/src/main/java/androidx/navigation/fragment/FragmentNavigator.kt

https://android-review.googlesource.com/2493203

Hi, i am also facing this issue after we dismiss a DialogFragment, the callback comes in the onPrepareOptionsMenu(), which is causing the issues for me.
Any idea on when it will be fixed?

Hello, any estimate please?

Facing a similar kind of issue when scrolling the fragments using a ViewPager.

https://issuetracker.google.com/issues/267677504

Can you update regarding any progress on this issue.

I wonder if the new SearchBar has this issue:
https://material.io/blog/android-stable-release-1-8-0

Project: platform/frameworks/support
Branch: androidx-main

commit 50f098644adc703ae218b0b7e999629f516a0241
Author: sanura <sanura@google.com>
Date:   Thu Mar 02 00:11:35 2023

    Add check to only invalidate options menu when contributing menu items
   
    FragmentManager previously appropriately only added
    a MenuProvider when the host is a MenuHost **and**
    we are at the root fragment that is providing the
    menu items. This behavior should be mirrored when
    removing a MenuProvider as well, so that only
    components that directly contribute menu items will
    invalidate the options menu.
   
    Bug: 244336571
    Test: all tests pass
    Change-Id: I9404ee9fcc9ce6b80d70a93bea720fe4ccf583a0

M       fragment/fragment/src/androidTest/java/androidx/fragment/app/FragmentContainerInflatedFragmentTest.kt
M       fragment/fragment/src/androidTest/java/androidx/fragment/app/OptionsMenuFragmentTest.kt
M       fragment/fragment/src/androidTest/java/androidx/fragment/app/test/FragmentTestActivity.kt
M       fragment/fragment/src/main/java/androidx/fragment/app/FragmentActivity.java
M       fragment/fragment/src/main/java/androidx/fragment/app/FragmentManager.java

https://android-review.googlesource.com/2465169

@13 Fixed when? On which version of which dependency?
Please show what to write on gradle file.

@15 I've noticed I can avoid using the fragment dependency and still work fine with fragments. How come?
It's part of the material dependency, perhaps?

@17 What if I don't use this dependency (probably imported automatically by material dependency) ? Use it, still?

@17 I wanted to try what you wrote on the sample I've provided (after I remove my workaround), and for some reason it doesn't let me.
It says "Duplicate class found".
The IDE doesn't provide any useful explanation of what is the class that is duplicated and what to do about it.
Please help.

@20 Not 1.6.0-alpha07 ?

@22 So it's fixed on both. OK