You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When I navigate to another screen and force the animations to be intentionally 3 seconds long, when I press back (on Android), it does not play the animation in the same speed, but only some sped-up version. This issue only happens when using native back button (on emulator for example) and not when calling navigateUp. Also, when I navigate back using system button during this long animation, the whole navigation breaks.
I am still trying to find the root cause of this.
Another case is that if you try to navigate to another scene while the transition is running, the transition also seems to be incorrect.
If i use androidx.activity.compose.BackHandler in actual android implementation, animation works as expected. But if I replace it with moe.tlaster.precompose.navigation.BackHandler, animation speed up
Describe the bug
When I navigate to another screen and force the animations to be intentionally 3 seconds long, when I press back (on Android), it does not play the animation in the same speed, but only some sped-up version. This issue only happens when using native back button (on emulator for example) and not when calling
navigateUp
. Also, when I navigate back using system button during this long animation, the whole navigation breaks.To Reproduce
Steps to reproduce the behavior:
AppNavigation
fileExpected behavior
Navigation animations work correctly regardless of if I navigate up using code or system buttons.
Minimal reproducible example
Mentioned in the first step
The text was updated successfully, but these errors were encountered: