Fixed
Status Update
Comments
il...@google.com <il...@google.com>
ro...@sparkistic.com <ro...@sparkistic.com> #2
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.
cu...@pocketprep.com <cu...@pocketprep.com> #3
Could you please describe how/where you changed your system to a manual setting?
al...@gmail.com <al...@gmail.com> #4
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.
al...@gmail.com <al...@gmail.com> #5
Comment has been deleted.
ap...@google.com <ap...@google.com> #6
voilà ce qu'on m'affiche lorsque j’exécute mon programme
de...@gmail.com <de...@gmail.com> #7
je ne vois pas comment résoudre ce problème. svp aidez moi
de...@gmail.com <de...@gmail.com> #8
I am still experiencing `exitAnim` not working when using `popUpTo` with the latest fragment-ktx:1.6.0 and navigation-fragment-ktx:2.5.1
jb...@google.com <jb...@google.com> #9
This has been fixed internally and will be available in the Fragment 1.5.2
release.
de...@gmail.com <de...@gmail.com> #10
How about for fragment-ktx:1.6.0 ?
Description
Component used: Fragment
Version used: 1.3.0, 1.4.0. Does not reproduce on 1.2.5.
Devices/Android versions reproduced on: Android Emulator.
Issue description
Given the following navigation graph:
Expected result:
I expect the following transition for the action
action_fragmentB_to_fragmentC
:@anim/fadeout
@anim/fadein
See
expected.mp4
attachment.This is what actually happens with fragment:1.2.5, but is broken in 1.3.0 and 1.4.0.
Actual result
From fragment:1.3.0 onwards, what happens is that, when
app:popUpTo="A"
is used, and while A is in the backstack, the transition for the actionaction_fragmentB_to_fragmentC
is different:@anim/slide_out_to_left
- Unexpected!@anim/fadein
It seems that the navigation component uses the
exitAnim
transition from the previously executed action,@id/action_fragmentA_to_fragmentB
.Removing
app:popUpTo="A"
from the action resolves the issue.See
actual.mp4
attachment.Reproducer
Attached minimal reproducer project:
NavigationAnimationTest.zip
.For swapping fragment versions, comment/uncomment the following
app/build.gradle
lines: