Fixed
Status Update
No update yet.
Comments
il...@google.com
to...@yahoo.com
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.
ap...@google.com
Could you please describe how/where you changed your system to a manual setting?
jb...@google.com
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.
Description
Component used: Fragment
Version used: 1.3.0-beta01
Devices/Android versions reproduced on: Pixel 2 API 29 emulator
Muzei's
mainmodule usesTRANSIT_FADEto swap between fragments based on whether Muzei is your current wallpaper. This listener is set on aFlowthat runs when the fragment is at leastSTARTED, meaning that callbacks end up normally being triggered as part of the move toSTARTED.Reproduction steps:
FragmentManager.enableNewStateManager(false)inMuzeiApplicationin themainmoduleExpected behavior: Next screen (
TutorialFragment) appearsActual behavior: New fragment does not appear, despite going to
RESUMEDstateAdditional information: If I attach the layout inspector, the fragment magically appears!
Removing the
TRANSIT_FADEor using the old state manager causes everything to work as expected as well.