Fixed
Status Update
No update yet.
Comments
[Deleted User] <[Deleted User]>
Please include a sample project that reproduces your issue.
vi...@google.com
vi...@google.com
il...@google.com
ap...@google.com
Here is the sample project.
Steps to reproduce:
1. Press on "Search" icon;
2. Write something;
3. Search this text, keyboard will be dismissed;
4. Tap on "Dialog" button;
5. Dissmiss dialog;
With the new 1.5.0 fragment library version text will be cleared in the search box after dismissing dialog.
In the version 1.4.1 and lower text in the search is not clearing and this is correct behaviour.
Please suggest some workarounds or how to fix this issue?
Steps to reproduce:
1. Press on "Search" icon;
2. Write something;
3. Search this text, keyboard will be dismissed;
4. Tap on "Dialog" button;
5. Dissmiss dialog;
With the new 1.5.0 fragment library version text will be cleared in the search box after dismissing dialog.
In the version 1.4.1 and lower text in the search is not clearing and this is correct behaviour.
Please suggest some workarounds or how to fix this issue?
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.