IssueTracker

Thank you Jeremy.

Since comment#13 is an issue different from comment#1, and it will be fixed by a new version of androidx.core as mentioned at comment#19, let's close this issue for now.

If the issue mentioned at comment#13 still happens, please feel free to file a new bug for it.

Any update on this to fix the crashing? Also does this new API will also fix the callback not being triggered after configuration change (orientation) for Android Tablet running on Android 21? We noticed another fragmented behavior between phone at tablet size devices where the setOnApplyWindowInsetsListener callback is not being triggered in Fragments after configuration change.

Activity (callback is being triggered on both phone and tablet after configuration change)

            ViewCompat.setOnApplyWindowInsetsListener(root) { _: View, insets: WindowInsetsCompat ->
                
                // Return WindowInsetsCompat.CONSUMED if you don't want the window insets to keep passing down
                // to descendant views including all views of Fragment(s) under this Activity
                insets
            }

Fragment with Jetpack Navigation (callback is being triggered regardless of Android version on phone size device after configuration change, but not on tablet running on Android 21)

            ViewCompat.setOnApplyWindowInsetsListener(root) { _: View, insets: WindowInsetsCompat ->
                
                // Return WindowInsetsCompat.CONSUMED if you don't want the window insets to keep passing down
                // to descendant views including all views of Fragment(s) under this Activity
                WindowInsetsCompat.CONSUMED
            }

Also hoping this to get fixed by this new API.

Any chance this issue gets higher priority? It's a shame that Google is forcing developers to migrate to Android 15 and setup edge-to-edge while still having critical compatibility issues with older Android versions even in apps with relatively modern stack (Fragment + Compose)

Hi Jeremy,

Do you have any update about the new release?

Build cut is this Wednesday and it will be released next week as part of Fragment 1.8.6.

OMG! Why is updatePadding API removed from Core KTX 1.16.0-beta01? It is the recommended approach to update padding in the docs. Its removal was not even mentioned in the release note and where did the ViewGroupCompat.installCompatInsetsDispatch(rootView) go? What is happening in the Android API?

Re comment#27:

Which library do you mean? If you mean fragment, I think you can find it here: https://developer.android.com/jetpack/androidx/releases/fragment#1.8.6