FragmentTransaction fade animation issue [175417675]

Fixed

Bug

NeedsInfo

Status Update

No update yet.

Description

jp...@gmail.com

created issue #1

Dec 12, 2020 07:09PM

Components used: Fragment, AppCompat
Fragment version used: 1.3.0-beta02
AppCompat version used: 1.3.0-alpha02
Devices/Android versions reproduced on: API 28 (device), API 30 (emulator)

The following code is resulting in animation flickering:

supportFragmentManager.beginTransaction()
        .setCustomAnimations(android.R.anim.fade_in, android.R.anim.fade_out)
        .show(fragment2)
        .hide(fragment1)
        .commit()

This seems like a regression, as using Fragment 1.2.5 and AppCompat 1.2.0 works as expected.

This bug can be reproduced in the following test project and is only noticeable when fading from fragment2 to fragment1:

https://github.com/jpmcosta/AndroidTestProject/tree/52623ada2aa61f8d3c3857612003f02126585388

A screen record of the issue is also attached.

Thank you for taking a look into this issue.

issue_fragment_transaction_fade_animation.mp4

821 KB

Download

Comments

il...@google.com <il...@google.com> Jan 8, 2021 12:10AM

Assigned to jb...@google.com.

ap...@google.com <ap...@google.com> #2Jan 19, 2021 07:55PM

Seems to be a DNS problem with systems that have 'obtain DNS server address automatically'. Changed my system to a manual setting and the browser etc now work. SDK 2.2 didn't seem to mind the auto setting though.

jb...@google.com <jb...@google.com> #3Jan 19, 2021 07:56PM

Marked as fixed.

Could you please describe how/where you changed your system to a manual setting?

jp...@gmail.com <jp...@gmail.com> #4Jan 19, 2021 08:11PM

Based on its date, this issue was originally reported before Android 2.3. Because of the many changes that existed in Android 4.x compared to previous versions, it's very likely that this issue doesn't exist in recent versions of Android like 4.2.2 or newer. Because of the high likelihood that this issue is obsolete, it is getting closed automatically by a script, without a human looking at it in detail. If the issue still exists on a Nexus 4 or Nexus 7 running Android 4.2.2 and is not related to Google applications, please open a new report accordingly.

Issue 175417675

Description

Issue summary

Comments

il...@google.com <il...@google.com> Jan 8, 2021 12:10AM

ap...@google.com <ap...@google.com> #2Jan 19, 2021 07:55PM

jb...@google.com <jb...@google.com> #3Jan 19, 2021 07:56PM

jp...@gmail.com <jp...@gmail.com> #4Jan 19, 2021 08:11PM

Add comment

Issue metadata