-
Notifications
You must be signed in to change notification settings - Fork 26.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Old screen transitions are used on Android API 28 #21191
Comments
Please add the output of |
Here's the output:
Though, these gifs are screen recordings of the vanilla messaging app from the Android emulator. |
Should be this closed as a result of #21715? |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
Here's what a slowed down version of an activity transition looks like on Android API 27. It's a slide up + fade in animation:
![api27-transition](https://user-images.githubusercontent.com/327631/44821063-adef9e80-abc1-11e8-834c-4f4f38d9445e.gif)
After #13736 is fixed (or using
MaterialPageRoute.debugEnableFadingRoutes = true
), this should match Flutter's current behavior.However, API 28 uses a different transition. It's a reveal + more subtle slide up animation:
![api28-transition](https://user-images.githubusercontent.com/327631/44821147-0aeb5480-abc2-11e8-9f89-260848b8ed74.gif)
MaterialPageRoute
should use a transition that is consistent with the API level.The text was updated successfully, but these errors were encountered: