Status Update
Comments
mo...@google.com <mo...@google.com> #2
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
mo...@google.com <mo...@google.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
ap...@google.com <ap...@google.com> #4
-
Second crash in the description is from a real device. Experienced it myself on two different Xiaomi phones, plus lots of crashes from users in the Google Play console.
-
Dynamic features are not used in the application.
As a wild guess, I have downgraded build tools from 31.0.0 to 30.0.3, compileSdk from 31 to 30, and moved all work with Language ID to the service in a separate process (just to be sure that crash can kill secondary process instead of main). This combination is in beta for 2 days by now and I don't see any SIGSEGV crashes.
na...@google.com <na...@google.com> #5
Hmm, I feel the crash might be something related to separate/secondary process.
I also changed compileSdk and targetSDK to 31 but still cannot repro this issue.
Description
Version used: 1.5.0-alpha01
Devices/Android versions reproduced on: API 34 device
When doing a Slide transition with Transition version `1.5.0-alpha01`, if you interrupt the transition the exiting View will jump a few pixels before sliding to the proper exit location creating an undesired effect. I am using a horizontal (Gravity.START) so it is unclear why the View would change vertically at all.
To reproduce, launch the app and click the next button and right before the transition completes, press it again.
I would expect that behavior to be consistent with what was in previous version which is no jump, and the transition smoothly reversing.