Crash (IndexOutOfBoundsException) on back navigation when using shared element transition with a viewgroup [188969304]

Fixed

Bug

NeedsInfo

Status Update

No update yet.

Description

dm...@gmail.com

created issue #1

May 22, 2021 11:00PM

Artifact used androidx.appcompat:appcompat:1.3.0: Version used: 1.3.0 Theme used: Default Devices/Android versions reproduced on: Google Pixel 3XL, Android 11

The code can be found in https://github.com/dmapr/fragment-1.3.4-bug
Screen recordings when building with appcompat-1.3.0 and appcompat-1.2.0 attached

It also appears that on appcompat-1.3.0 only the ViewGroup containing the text is transitioning, the standalone ImageView included in the transition is ignored. The appcompat-1.2.0 transitions both views properly.

05-22 15:51:09.968  7068  7068 E AndroidRuntime: FATAL EXCEPTION: main
05-22 15:51:09.968  7068  7068 E AndroidRuntime: Process: com.rnd8x8.fragment_134_bug, PID: 7068
05-22 15:51:09.968  7068  7068 E AndroidRuntime: java.lang.IndexOutOfBoundsException: Index: 3, Size: 3
05-22 15:51:09.968  7068  7068 E AndroidRuntime:        at java.util.ArrayList.get(ArrayList.java:437)
05-22 15:51:09.968  7068  7068 E AndroidRuntime:        at androidx.fragment.app.FragmentTransitionImpl.setNameOverridesReordered(FragmentTransitionImpl.java:183)
05-22 15:51:09.968  7068  7068 E AndroidRuntime:        at androidx.fragment.app.DefaultSpecialEffectsController.startTransitions(DefaultSpecialEffectsController.java:665)
05-22 15:51:09.968  7068  7068 E AndroidRuntime:        at androidx.fragment.app.DefaultSpecialEffectsController.executeOperations(DefaultSpecialEffectsController.java:114)
05-22 15:51:09.968  7068  7068 E AndroidRuntime:        at androidx.fragment.app.SpecialEffectsController.executePendingOperations(SpecialEffectsController.java:294)
05-22 15:51:09.968  7068  7068 E AndroidRuntime:        at androidx.fragment.app.Fragment$3.run(Fragment.java:2780)
05-22 15:51:09.968  7068  7068 E AndroidRuntime:        at android.os.Handler.handleCallback(Handler.java:938)
05-22 15:51:09.968  7068  7068 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:99)
05-22 15:51:09.968  7068  7068 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:223)
05-22 15:51:09.968  7068  7068 E AndroidRuntime:        at android.app.ActivityThread.main(ActivityThread.java:7660)
05-22 15:51:09.968  7068  7068 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
05-22 15:51:09.968  7068  7068 E AndroidRuntime:        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
05-22 15:51:09.968  7068  7068 E AndroidRuntime:        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)

shared-element-transition-appcompat-1.2.0.mp4

1.2 MB

Download

shared-element-transition-appcompat-1.3.0.mp4

3.1 MB

Download

Comments

dm...@gmail.com <dm...@gmail.com> #2May 23, 2021 07:22PM

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

ow...@google.com <ow...@google.com> #3May 25, 2021 03:40PM

It sounds like this is a behavior change between fragment:1.3.3 and fragment-1.3.4 which bumping appcompat pulls in.

dm...@gmail.com <dm...@gmail.com> #4May 25, 2021 03:57PM

Yes, I'm 99% sure it's a side-effect of this commit: https://android-review.googlesource.com/q/I99675eac030325415789be0762aa666355f27dd8

il...@google.com <il...@google.com> Jun 8, 2021 07:52PM

Assigned to jb...@google.com.

ap...@google.com <ap...@google.com> #5Jun 9, 2021 11:46PM

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

commit 06769a572f7003fb662109b595952d6ff5c63a74
Author: Jeremy Woods <jbwoods@google.com>
Date: Tue Jun 08 16:35:28 2021

Fix fragment transitions in new state manager

In aosp/1679887 we attempted to fix doing shared element transitions on
ViewGroups with the transitionGroup="false" attribute set. That change
caused a regression in enter and exit transitions, and could also cause
errors if the entering fragment attempted to transition more views than
the exiting fragment.

This change makes it so that fragments no longer looks at all of the
views in the hierarchy of sharedelement views. We depend on transition
names to determine if a view is a shared element, and if a shared
element is a viewgroup with transitionGroup="true", the entering/exiting
transition should ignore that viewgroup and transition its unnamed
children.

RelNote: "Fixed regression in shared element transtions caused by
aosp/1679887. Setting transitionGroup=\"true\" will now work correctly and
shared elements will no longer throw `IndexOutOfBoundsException`s."
Test: FragmentSharedElementTransitionTest
Bug: 188679569
Bug: 188969304

Change-Id: I164845639cae1f64cf54e4e89b2a24d7eb649beb

M fragment/fragment/src/androidTest/java/androidx/fragment/app/FragmentSharedElementTransitionTest.kt
A fragment/fragment/src/androidTest/res/layout/scene6.xml
A fragment/fragment/src/androidTest/res/layout/scene7.xml
M fragment/fragment/src/main/java/androidx/fragment/app/DefaultSpecialEffectsController.java

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

jb...@google.com <jb...@google.com> #6Jun 10, 2021 01:51AM

Marked as fixed.

This has been fixed internally and will be part of the Fragment 1.4.0-alpha03 release. You can verify that it works with your app by following the instructions at androidx.dev to enable SNAPSHOTs and using a buildId of 7444280+.

eu...@gmail.com <eu...@gmail.com> #7Sep 1, 2021 09:44AM

would the fix be backported to 1.3.x?

dm...@gmail.com <dm...@gmail.com> #8Sep 1, 2021 03:27PM

The fix has been available since 1.3.5: https://developer.android.com/jetpack/androidx/releases/fragment#1.3.5