Status Update
Comments
su...@google.com <su...@google.com> #2
Jeremy, is this still an issue? I think the problem was that you had two transitions targeting the same View for the same action (e.g. two Slide() transitions).
qu...@gmail.com <qu...@gmail.com> #3
I have a similar issue with plain AnimatorSet:
set.start()
set.pause()
set.setCurrentPlayTime(100)
set.setCurrentPlayTime(0)
set.setCurrentPlayTime(100)
set.resume()
doesn't play animation in resume().
jb...@google.com <jb...@google.com> #4
Should clarify that if I filter out setCurrentPlayTime(0)
(or replace it with setCurrentPlayTime(1)
) it works well.
Also even with setCurrentPlayTime(0)
, onAnimationEnd
is notified with correct delay (as if the animation has played).
qu...@gmail.com <qu...@gmail.com> #5
@
I think that is intended for Animator. If you set the currentPlayTime
to 0 or the total duration the animator completes. We do some
jb...@google.com <jb...@google.com> #6
Did some investigation on the Fragment side and it seems like the merged transition is targeting correctly.
Exiting Transition: Slide@aa9288e: tgts(android.widget.LinearLayout{f9add3d})
>>>>> ExitingViews <<<<<
View: android.widget.LinearLayout{f9add3d}
Entering Transition: Slide@35b8af: tgts(android.widget.LinearLayout{b7f24bc})
>>>>> EnteringViews <<<<<
View: android.widget.LinearLayout{b7f24bc}
Final merged transition: TransitionSet@7bc1c45:
TransitionSet@e133f9a:
Slide@aa9288e: tgts(android.widget.LinearLayout{f9add3d})
Slide@35b8af: tgts(android.widget.LinearLayout{b7f24bc})
merged transition passed to controlDelayedTransition: TransitionSet@7bc1c45:
TransitionSet@e133f9a:
Slide@aa9288e: tgts(android.widget.LinearLayout{f9add3d})
Slide@35b8af: tgts(android.widget.LinearLayout{b7f24bc})
Still digging.
qu...@gmail.com <qu...@gmail.com> #7
Branch: androidx-main
commit 567b7459329d1ec8d27a8c6fe1c4a86442065d7d
Author: Jeremy Woods <jbwoods@google.com>
Date: Tue Sep 26 20:06:54 2023
Add additional logging for transitions
Adding more debug logging in transitions to track the entering and
exiting transitions as well as the final merged transition and its
targets.
Test: added logging
Bug: 300157785
Change-Id: I0d9ad72b865422493c6c895ddb6115abf85eed16
M fragment/fragment/src/main/java/androidx/fragment/app/DefaultSpecialEffectsController.kt
jb...@google.com <jb...@google.com> #8
So I have isolated this outside of fragment into something much simpler and I think it breaks down when it comes to the adding and removing of Views with animateToStart.
The attached sample is a simple add that goes between two screens BLUE
and GREEN
. It has code for both the 1.5.0-alpha03
and 1.5.0-alpha04
versions, but I think alpha04 is currently broken in another way so I will upload the alpha03 version here.
This is integrated with predictive back similar to how fragment is, so upon cancelling we call animateToStart
, then we do a beginDelayedTransition
on a 0
duration Fade()
and we reverse the view visibility back to what it was prior to starting the transition.
If you only do visibility, cancel always works the view never goes away, it is wonderful, but when you do adding and removing views like we need to in fragment it fails.
First the code for beginDelayedTransition goes from this:
TransitionManager.beginDelayedTransition(container, Fade().apply {
duration = 0
})
reverseViews()
to this:
TransitionManager.beginDelayedTransition(container, Fade().apply {
duration = 0
addListener(onEnd = {
reverseViews()
blueScreen.visibility = View.VISIBLE
greenScreen.visibility = View.VISIBLE
})
})
reverseViews(useVisibility = true)
We need to make this change because after the animateToStart()
view is still parented by the overlay, so we call reverseViews(useVisibility = true)
to only change the visibility and then once the transition finishes we can call reverseViews()
to parent the view properly, then we make both views visible again.
From our perspective after the 0
duration transition our views are back in the proper state, but they do not transition properly after a cancel.
If the app is doing this wrong and we can make the appropriate fixes, doing the same in fragment should resolve this. There is logging available that shows the state of the views when we start the transition.
qu...@gmail.com <qu...@gmail.com> #9
The API has changed since that project was created in a way that makes the API more robust. I'm hoping that has fixed this...
jb...@google.com <jb...@google.com> #10
There appears to be a problem with the order of operations. I'm going to look into fixing that.
qu...@gmail.com <qu...@gmail.com> #11
Branch: androidx-main
commit e57dd5f9ac6cbb8cf83b221e2d5b3fbd3e88ce6b
Author: George Mount <mount@google.com>
Date: Thu Nov 09 14:33:53 2023
Fix animateToStart with Slide.
Fixes: 300157785
Slide was not repositioning the View to its proper
translation after animating it to the start position.
This fixes that so that it is moved.
Test: new test
Change-Id: I698f4dbcef46304f9aa545847d205f7b70c80d63
M transition/transition/src/androidTest/java/androidx/transition/SlideEdgeTest.java
M transition/transition/src/androidTest/java/androidx/transition/TranslationAnimationCreatorTest.java
M transition/transition/src/main/java/androidx/transition/TranslationAnimationCreator.java
jb...@google.com <jb...@google.com>
ap...@google.com <ap...@google.com> #12
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.transition:transition:1.5.0-alpha05
qu...@gmail.com <qu...@gmail.com> #13
sa...@google.com <sa...@google.com> #14
This has been fixed internally and will be available in Lifecycle 2.6.0-alpha03
il...@google.com <il...@google.com>
re...@livedrive.com <re...@livedrive.com> #15
na...@google.com <na...@google.com> #16
The following release(s) address this bug:
androidx.lifecycle:lifecycle-runtime:2.6.0-alpha03
qu...@gmail.com <qu...@gmail.com> #17
Fatal Exception: java.lang.IllegalStateException: no event down from INITIALIZED in component d{7f1b10e} (0b387363-3c6b-4f7d-af8f-22ebafc87084 id=0x7f0a0302 tag=a::)
il...@google.com <il...@google.com> #18
Re d
is in your app, following the 'You can identify your Fragment' section in the
qu...@gmail.com <qu...@gmail.com> #19
mi...@gmail.com <mi...@gmail.com> #20
androidx.lifecycle:lifecycle-runtime:2.6.0-alpha03
androidx.navigation:navigation-fragment-ktx:2.5.3
androidx.navigation:navigation-ui-ktx:2.5.3
and got crash:
java.lang.RuntimeException: Unable to destroy activity {<package name hidden by me>.MainActivity}: java.lang.IllegalStateException: no event down from INITIALIZED in component androidx.navigation.NavBackStackEntry
with reason:
Caused by: java.lang.IllegalStateException: no event down from INITIALIZED in component androidx.navigation.NavBackStackEntry
(I see that issue is connected with NavBackStackEntry thanks update to :lifecycle-runtime:2.6.0-alpha03)
In my MainActivity there is NavHostFragment with NavController and queue of NavBackStackEntries inside.
When I navigate from Acitivity to some fragment using code below:
Log.i("showSomeFragment","state just before navigate: ${findNavController().currentBackStackEntry?.lifecycle?.currentState}")
findNavController().navigate(
MainNavgraphDirections.actionShowSomeFragment(...)
)
Log shows that NavBackStackEntry's lifecycle's is in state RESUMED, but in target fragment's onCreate (after navigation)
NavBackStackEntry's lifecycle's is in state INITIALIZED
Therefore, when I minimize app being on that fragment - app crashes, because I go from INITIALIZED to DESTROYED state (skipping other states).
When I navigate similarly between fragments (using findNavController().navigate in fragment, not in activity) ->
NavBackStackEntry's lifecycle's state is in state RESUMED in target's fragment onCreate an there is no crash after minimize.
Do I don't understand something/do you have any hints for that, or there is bug in navigation library?
For clarity: Yes, I understand that when we go from INITIALIZED directly to DESTROYED state - error SHOULD be thrown
fr...@gmail.com <fr...@gmail.com> #21
il...@google.com <il...@google.com> #22
Re
pe...@gmail.com <pe...@gmail.com> #23
Fatal Exception: java.lang.RuntimeException: Unable to destroy activity {path to MainActivity}: java.lang.IllegalStateException: no event down from INITIALIZED
at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:5253)
at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:5282)
at android.app.servertransaction.DestroyActivityItem.execute(DestroyActivityItem.java:44)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2146)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:236)
at android.app.ActivityThread.main(ActivityThread.java:8057)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:656)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:967)
il...@google.com <il...@google.com> #24
Re
en...@gmail.com <en...@gmail.com> #25
ah...@gmail.com <ah...@gmail.com> #26
pu...@grabtaxi.com <pu...@grabtaxi.com> #27
pu...@grabtaxi.com <pu...@grabtaxi.com> #28
Hi also having the same problem here, and not able to reproduce it locally, seems from the log that it happened when onBackPressed is triggered. I have tried to put dismiss
inside init
function of my dialog fragment also not able to reproduce it. Is there any thing I can look into?
I'm using
Lifecycle 2.6.1, happened as well in 2.5.1
androidx.lifecycle.LifecycleRegistry.moveToState (LifecycleRegistry.kt:126)
androidx.lifecycle.LifecycleRegistry.handleLifecycleEvent (LifecycleRegistry.kt:119)
androidx.activity.ComponentDialog.onStop (ComponentDialog.kt:87)
androidx.appcompat.app.AppCompatDialog.onStop (AppCompatDialog.java:134)
android.app.Dialog.dismissDialog (Dialog.java:382)
android.app.Dialog.dismiss (Dialog.java:358)
androidx.appcompat.app.AppCompatDialog.dismiss (AppCompatDialog.java:140)
android.app.Dialog.cancel (Dialog.java:1269)
android.app.Dialog.onBackPressed (Dialog.java:684)
androidx.activity.ComponentDialog.onBackPressedDispatcher$lambda$1 (ComponentDialog.kt:94)
androidx.activity.OnBackPressedDispatcher.onBackPressed (OnBackPressedDispatcher.kt:216)
androidx.activity.ComponentDialog.onBackPressed (ComponentDialog.kt:99)
android.app.Dialog.onKeyUp (Dialog.java:661)
android.view.KeyEvent.dispatch (KeyEvent.java:2729)
android.app.Dialog.dispatchKeyEvent (Dialog.java:814)
androidx.appcompat.app.AppCompatDialog.superDispatchKeyEvent (AppCompatDialog.java:209)
androidx.core.view.KeyEventDispatcher.dispatchKeyEvent (KeyEventDispatcher.java:86)
androidx.appcompat.app.AppCompatDialog.dispatchKeyEvent (AppCompatDialog.java:215)
androidx.appcompat.view.WindowCallbackWrapper.dispatchKeyEvent (WindowCallbackWrapper.java:60)
androidx.appcompat.app.AppCompatDelegateImpl$AppCompatWindowCallback.dispatchKeyEvent (AppCompatDelegateImpl.java:3413)
com.android.internal.policy.DecorView.dispatchKeyEvent (DecorView.java:346)
android.view.ViewRootImpl$ViewPostImeInputStage.processKeyEvent (ViewRootImpl.java:5214)
android.view.ViewRootImpl$ViewPostImeInputStage.onProcess (ViewRootImpl.java:5082)
android.view.ViewRootImpl$InputStage.deliver (ViewRootImpl.java:4601)
android.view.ViewRootImpl$InputStage.onDeliverToNext (ViewRootImpl.java:4654)
android.view.ViewRootImpl$InputStage.forward (ViewRootImpl.java:4620)
android.view.ViewRootImpl$AsyncInputStage.forward (ViewRootImpl.java:4760)
android.view.ViewRootImpl$InputStage.apply (ViewRootImpl.java:4628)
android.view.ViewRootImpl$AsyncInputStage.apply (ViewRootImpl.java:4817)
android.view.ViewRootImpl$InputStage.deliver (ViewRootImpl.java:4601)
android.view.ViewRootImpl$InputStage.onDeliverToNext (ViewRootImpl.java:4654)
android.view.ViewRootImpl$InputStage.forward (ViewRootImpl.java:4620)
android.view.ViewRootImpl$InputStage.apply (ViewRootImpl.java:4628)
android.view.ViewRootImpl$InputStage.deliver (ViewRootImpl.java:4601)
android.view.ViewRootImpl$InputStage.onDeliverToNext (ViewRootImpl.java:4654)
android.view.ViewRootImpl$InputStage.forward (ViewRootImpl.java:4620)
android.view.ViewRootImpl$AsyncInputStage.forward (ViewRootImpl.java:4793)
android.view.ViewRootImpl$ImeInputStage.onFinishedInputEvent (ViewRootImpl.java:4956)
android.view.inputmethod.InputMethodManager$PendingEvent.run (InputMethodManager.java:2580)
android.view.inputmethod.InputMethodManager.invokeFinishedInputEventCallback (InputMethodManager.java:2090)
android.view.inputmethod.InputMethodManager.finishedInputEvent (InputMethodManager.java:2081)
android.view.inputmethod.InputMethodManager$ImeInputEventSender.onInputEventFinished (InputMethodManager.java:2557)
android.view.InputEventSender.dispatchInputEventFinished (InputEventSender.java:141)
android.os.MessageQueue.nativePollOnce (MessageQueue.java)
android.os.MessageQueue.next (MessageQueue.java:326)
android.os.Looper.loop (Looper.java:165)
android.app.ActivityThread.main (ActivityThread.java:6861)
java.lang.reflect.Method.invoke (Method.java)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:547)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:873)
Description
Fatal Exception: java.lang.IllegalStateException: no event down from INITIALIZED
at androidx.lifecycle.LifecycleRegistry.moveToState(LifecycleRegistry.java:35)
at androidx.lifecycle.LifecycleRegistry.handleLifecycleEvent(LifecycleRegistry.java:9)
at androidx.fragment.app.Fragment.performDestroy(Fragment.java:9)
at androidx.fragment.app.FragmentStateManager.destroy(FragmentStateManager.java:147)
at androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:266)
at androidx.fragment.app.SpecialEffectsController$FragmentStateManagerOperation.complete(SpecialEffectsController.java:5)
at androidx.fragment.app.SpecialEffectsController$Operation.cancel(SpecialEffectsController.java:18)
at androidx.fragment.app.SpecialEffectsController.forceCompleteAllOperations(SpecialEffectsController.java:228)
at androidx.fragment.app.SpecialEffectsController.executePendingOperations(SpecialEffectsController.java:14)
at androidx.fragment.app.FragmentManager.executeOpsTogether(FragmentManager.java:268)
at androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute(FragmentManager.java:81)
at androidx.fragment.app.FragmentManager.execPendingActions(FragmentManager.java:21)
at androidx.fragment.app.FragmentManager.dispatchStateChange(FragmentManager.java:38)
at androidx.fragment.app.FragmentManager.dispatchActivityCreated(FragmentManager.java:11)
at androidx.fragment.app.FragmentController.dispatchActivityCreated(FragmentController.java:4)
at androidx.fragment.app.FragmentActivity.onStart(FragmentActivity.java:20)
at androidx.appcompat.app.AppCompatActivity.onStart(AppCompatActivity.java)
at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1435)
at android.app.Activity.performStart(Activity.java:8231)
at android.app.ActivityThread.handleStartActivity(ActivityThread.java:3872)
at android.app.servertransaction.TransactionExecutor.performLifecycleSequence(TransactionExecutor.java:221)
at android.app.servertransaction.TransactionExecutor.cycleToPath(TransactionExecutor.java:201)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:173)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2336)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:246)
at android.app.ActivityThread.main(ActivityThread.java:8653)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:602)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1130
or
Fatal Exception: java.lang.IllegalStateException: no event down from INITIALIZED
at androidx.lifecycle.LifecycleRegistry.moveToState(LifecycleRegistry.java:35)
at androidx.lifecycle.LifecycleRegistry.handleLifecycleEvent(LifecycleRegistry.java:9)
at androidx.fragment.app.Fragment.performDestroy(Fragment.java:9)
at androidx.fragment.app.FragmentStateManager.destroy(FragmentStateManager.java:147)
at androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:266)
at androidx.fragment.app.SpecialEffectsController$FragmentStateManagerOperation.complete(SpecialEffectsController.java:5)
at androidx.fragment.app.SpecialEffectsController$Operation.cancel(SpecialEffectsController.java:18)
at androidx.fragment.app.SpecialEffectsController.forceCompleteAllOperations(SpecialEffectsController.java:228)
at androidx.fragment.app.SpecialEffectsController.executePendingOperations(SpecialEffectsController.java:14)
at androidx.fragment.app.FragmentManager.executeOpsTogether(FragmentManager.java:268)
at androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute(FragmentManager.java:81)
at androidx.fragment.app.FragmentManager.execPendingActions(FragmentManager.java:21)
at androidx.fragment.app.FragmentManager.dispatchStateChange(FragmentManager.java:38)
at androidx.fragment.app.FragmentManager.dispatchActivityCreated(FragmentManager.java:11)
at androidx.fragment.app.FragmentController.dispatchActivityCreated(FragmentController.java:4)
at androidx.fragment.app.FragmentActivity.onStart(FragmentActivity.java:20)
at androidx.appcompat.app.AppCompatActivity.onStart(AppCompatActivity.java)
at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1391)
at android.app.Activity.performStart(Activity.java:7348)
at android.app.ActivityThread.handleStartActivity(ActivityThread.java:3138)
at android.app.servertransaction.TransactionExecutor.performLifecycleSequence(TransactionExecutor.java:180)
at android.app.servertransaction.TransactionExecutor.cycleToPath(TransactionExecutor.java:165)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:142)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:70)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1948)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:214)
at android.app.ActivityThread.main(ActivityThread.java:7050)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:494)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:965)
(about 50 different lines with the same stack)
Since it comes 100% from Google code there's nothing we can do about it, unless of course someone could explain what " no event down from INITIALIZED" means...