IssueTracker

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

commit b9b1326edfe38588a9882e1ee624798966c5686a
Author: Jeremy Woods <jbwoods@google.com>
Date:   Wed Oct 06 16:49:53 2021

    Clear focus on Fragments animating out
   
    Since moving to the new state manager, fragment now explicitly handle
    focus where in the old world they could ignore it altogether. This
    change has the side effect that other things affected by focus (i.e.
    soft keyboard input) are affect as well. In particular when we
    requestFocus we update the input request, but since we never clear it
    users have to manually remove the input.
   
    When we are animating a fragment view out, since we will no longer be
    using the exiting view, let clear the focus of before we remove it from
    the fragment.
   
    RelNote: "The keyboard will now close automatically when going from
    a fragment with an open keyboard to a fragment with a recycler view."
    Test: tested in sample app from bug
    Bug: 196852211
   
    Change-Id: I8b842dd9a421cfbc9189014b802f5e4b6b9c2a47

M       fragment/fragment/src/main/java/androidx/fragment/app/SpecialEffectsController.java

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

The issue still persist in API version 27 and below in Fragment 1.4.0

Any workaround anyone?

I am having the same error
Nexus 5, android 6.0.1, support library 24.0.0.

Probably related to https://code.google.com/p/android/issues/detail?id=208911

and to https://code.google.com/p/android/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Status%20Priority%20Owner%20Summary%20Stars%20Reporter%20Opened&groupby=&sort=&id=218912

Still around in 'com.android.support:support-v4:24.2.0'
Does anyone has any workaround for this?

Thanks!

This story has been merged into https://code.google.com/p/android/issues/detail?id=218912

[Comment deleted]

Still around in 'com.android.support:support-v4:24.2.1'

Does anyone got any workaround for this?

do your turn on  dont keep activities in Developer options?.
if true,see this https://testsmirk.com/2016/10/14/android-viewpager-bug/

Googlers it is shame that the bug is there in view pager more than 3 years.  Why don't you take seriously? Fix it guys can't wait more time

This works for me:

    @Override
    protected void onDestroy() {
        Log.d(TAG, "onDestroy");
          try {
            super.onDestroy();
        } catch (NullPointerException npe) {
            Log.e(TAG, "NPE: Bug workaround");
        }

 java.lang.IllegalStateException: FragmentManager is already executing transactions
                                                                       at android.support.v4.app.FragmentManagerImpl.execSingleAction(FragmentManager.java:1620)
                                                                       at android.support.v4.app.BackStackRecord.commitNowAllowingStateLoss(BackStackRecord.java:637)
                                                                       at android.support.v4.app.FragmentPagerAdapter.finishUpdate(FragmentPagerAdapter.java:143)
                                                                       at android.support.v4.view.ViewPager.populate(ViewPager.java:1237)
                                                                       at android.support.v4.view.ViewPager.populate(ViewPager.java:1085)
                                                                       at android.support.v4.view.ViewPager.onMeasure(ViewPager.java:1611)
                                                                       at android.view.View.measure(View.java:18850)
                                                                       at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5963)
                                                                       at android.widget.FrameLayout.onMeasure(FrameLayout.java:194)
                                                                       at android.view.View.measure(View.java:18850)
                                                                       at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5963)
                                                                       at android.widget.LinearLayout.measureChildBeforeLayout(LinearLayout.java:1465)
                                                                       at android.widget.LinearLayout.measureVertical(LinearLayout.java:748)
                                                                       at android.widget.LinearLayout.onMeasure(LinearLayout.java:630)
                                                                       at android.view.View.measure(View.java:18850)
                                                                       at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5963)
                                                                       at android.widget.FrameLayout.onMeasure(FrameLayout.java:194)
                                                                       at android.view.View.measure(View.java:18850)
                                                                       at android.support.v4.widget.DrawerLayout.onMeasure(DrawerLayout.java:1079)
                                                                       at android.view.View.measure(View.java:18850)
                                                                       at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5963)
                                                                       at android.widget.FrameLayout.onMeasure(FrameLayout.java:194)
                                                                       at android.support.v7.widget.ContentFrameLayout.onMeasure(ContentFrameLayout.java:135)
                                                                       at android.view.View.measure(View.java:18850)

[Comment deleted]

[Comment deleted]

I am seeing similar behavior as #16. Seeing similar crash trying to mask it. @Android guys any resolutions on this?