Fixed
Status Update
No update yet.
Comments
[Deleted User] <[Deleted User]>
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Android build
Which Android build are you using? (e.g. OPP1.170223.012)
Device used
Which device did you use to reproduce this issue?
Steps to reproduce
What steps are needed to reproduce this issue?
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Android bug report capturing
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method
After reproducing the issue, navigate to “developer settings”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Screen capture of the issue
Press the volume down and power buttons simultaneously. The image will appear in your gallery. Attach the screenshot file to this issue.
NOTE : To avoid leaking private information, please share screenshots and bugreports only in Google Drive. Share files with android-bugreport@google.com and include only Google drive links in your bug. Bug report attachments should not be included directly in issue reports.
Android build
Which Android build are you using? (e.g. OPP1.170223.012)
Device used
Which device did you use to reproduce this issue?
Steps to reproduce
What steps are needed to reproduce this issue?
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Android bug report capturing
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method
After reproducing the issue, navigate to “developer settings”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Screen capture of the issue
Press the volume down and power buttons simultaneously. The image will appear in your gallery. Attach the screenshot file to this issue.
NOTE : To avoid leaking private information, please share screenshots and bugreports only in Google Drive. Share files with android-bugreport@google.com and include only Google drive links in your bug. Bug report attachments should not be included directly in issue reports.
Description
androidX version: androidx.appcompat:appcompat:1.1.0-alpha04
It's not easy to reproduce this bug. But I can show you guys the stack when crash occured:
#main(1)
ComponentActivity.java:288
Caused by:androidx.activity.ComponentActivity.onBackPressed
Can not perform this action after onSaveInstanceState
Fatal Exception:java.lang.IllegalStateException
androidx.activity.ComponentActivity.onBackPressed(ComponentActivity.java:288)
android.app.Activity.onBackPressed(Activity.java:2523)
android.app.FragmentManagerImpl.popBackStackImmediate(FragmentManagerImpl.java:498)
android.app.FragmentManagerImpl.checkStateLoss(FragmentManagerImpl.java:1337)
stack above is the crash point. Focus on the last line, the point where exception was thrown is at checkStateLoss. why this, I found the reason.
link:
Older versions will throw an exception from the framework {@code FragmentManager.popBackStackImmediate}, but the commit above remove these workaround code. you can review the change by the link above or open the picture in the attachment.
I know the code related in 1.1.0 stable version was changed and you guys refactor this already, but I still can not find the workaround code so you guys should check this problem with 1.1.0-alpha04 and newest code both.