Assigned
Status Update
No update yet.
Comments
ra...@google.com
Information redacted by Android Beta Feedback.
ra...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Complete steps to reproduce
What steps do others need to take in order to reproduce the issue themselves?
Current output (Error message if any)
What do you see instead?
Screen Record of the Issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
Complete steps to reproduce
What steps do others need to take in order to reproduce the issue themselves?
Current output (Error message if any)
What do you see instead?
Screen Record of the Issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue
Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.
Description
Component used: Activity
Version used:(Specify the Jetpack Activity version, e.g., 1.8.0)
Devices/Android versions reproduced on:(List affected devices and Android versions, e.g., Pixel 6, Android 14) Steps to reproduce:
Launch the app with an Activity.
Perform a configuration change (e.g., rotate the screen or change system theme).
Observe that the Activity unexpectedly gets recreated, even when android:configChanges is specified in the manifest. Expected behavior: The Activity should not be recreated if android:configChanges="orientation|screenSize" is set.
Actual behavior: The Activity gets recreated, causing UI state loss.
Additional info:
Reproducible on different Android versions.
Issue persists even with ViewModel and SavedStateHandle.
If this is a bug in the library, we would appreciate if you could attach: