IssueTracker

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

commit 57ca221882695bd6a52549f4d9ea3b812e6fe87c
Author: Simon Schiller <simonschiller@users.noreply.github.com>
Date:   Mon Mar 22 16:09:30 2021

    [GH] [FragmentStrictMode] Detect <fragment> tag usage
   
    ## Proposed Changes
   
      - Detect `<fragment>` tag usage inside XML layouts
   
    ## Testing
   
    Test: See `FragmentStrictModeTest#detectFragmentTagUsage`
   
    ## Issues Fixed
   
    Fixes: 153738235
   
    This is an imported pull request from https://github.com/androidx/androidx/pull/141.
   
    Resolves #141
    Github-Pr-Head-Sha: 4ea052596e4341b9f11bcf335e2bc38045a91f19
    GitOrigin-RevId: 62e7487aa4874eef6bb556490e193717cf937251
    Change-Id: Iae48578e85e4e4897f806d7ade2e2a660adf9479

M       fragment/fragment/api/public_plus_experimental_current.txt
M       fragment/fragment/api/restricted_current.txt
M       fragment/fragment/src/androidTest/java/androidx/fragment/app/strictmode/FragmentStrictModeTest.kt
M       fragment/fragment/src/main/java/androidx/fragment/app/FragmentLayoutInflaterFactory.java
M       fragment/fragment/src/main/java/androidx/fragment/app/strictmode/FragmentStrictMode.java
A       fragment/fragment/src/main/java/androidx/fragment/app/strictmode/FragmentTagUsageViolation.java

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

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

commit c250706435c04194eebb0f22168cad3e71ae6969
Author: Jeremy Woods <jbwoods@google.com>
Date:   Mon Sep 11 18:43:01 2023

    Actually turn on seeking for Androidx Transitions
   
    We need to make sure the isSeekingSupport API with no params returns
    true for AndroidX transitions.
   
    Test: existing tests pass
    Bug: 285175724
    Change-Id: I1136e51712b09795b0d422ee93bc0a9cfd3e21e9

M       transition/transition/src/main/java/androidx/transition/FragmentTransitionSupport.java

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

I don't understand how this is fixed. Is there any sample of how to use this ?
Can the new predictive-back-gesture be applied nicely for Fragments inside navigation container, so that even when navigating between them, you will see what's behind, just like for Activities?

@6 Can you please show how it's done?
Or even better:
Change the new app wizard and have it there with a checkbox to support the new  predictive-back-gesture?

@8 Not sure I see there about Fragments in navigation component, of how to handle it there.
It's mostly about Activities.

Also, speaking of Activities, I can't find a way to support it only to some Activities. Currently it's all-or-nothing, making it very hard to migrate to it and also reduce the appeal of migrating to it (as it requires the entire project to migrate, instead of just what matters).

@9 Please also show samples in fragments within navigation.
In the past when I talked about it, Google actually said (maybe even here in the issue tracker) that it's denied and won't be added.
I don't understand what's going on now.

@12 Was it added recently? I don't remember seeing this.
About the samples, please also add for navigation and maybe also for the navigation-drawer sample.
Even better if you put it in the templates of a new Activity, as this way you could encourage developers to do it.

@14 OK thank you. I wish you'd restore some of the templates there, to show how to use them nowadays.
I learn better from tiny samples than large ones. And those that are shown "on the way" right in the templates of the IDE mean you are serious about them.

Please make sure that we can have all of the possible behaviors of the Predictive Back Gesture when used in a fragment withing the navigation graph:
1. Show the fragment that we will go to when trying to go back
2. Block going to previous fragment (either doesn't exist, or exist and we choose not to allow it) and instead show what's behind in terms of Activity (or app), instead (leaving the current Activity/app)
3. Block back gesture completely, not allowing to go back

Will you please also fix the countless of weird exceptions that appear to this day even on Android 14, related to foreground service?
I've been struggling with it for a very long time. Even found some scenarios for some of the exceptions to occur, and some even contradict the documentation, including even on Pixel devices...

@14 The blocking to going to previous Fragment is important in case the previous Fragment is used as a way to choose which Fragment to reach, and not as UI.
This is something that was said to use instead of clearing the stack itself:
https://issuetracker.google.com/issues/109909461#comment5
https://developer.android.com/guide/navigation/use-graph/conditional

So you wouldn't want to show the MainFragment there, and instead you'd want to allow to skip directly to the Activity behind, even though MainFragment is in the back-stack of the navigation.

Sadly even there on this documentation, there is no sample and there is a lot of missing code.