We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
State is lost instead of being restored after process death on "First Screen (type.fragment, internal)".
Happens both if in front, or if it is on the backstack.
1.) add input text
2.) put app in background
3.) adb -s 04UAY1WGLN shell am kill com.turo.nibel.sample
adb -s 04UAY1WGLN shell am kill com.turo.nibel.sample
(this is my device id with the -s yours might differ or you might not even need it)
-s
4.) open app from launcher
App should be exactly as before, but on "First Screen" the text input is lost.
The text was updated successfully, but these errors were encountered:
Good catch, thanks for opening the issue. It would be a good idea to retain the input text value in this case indeed.
This would be an update on a sample app's level, but it is definitely worth doing.
Sorry, something went wrong.
No branches or pull requests
State is lost instead of being restored after process death on "First Screen (type.fragment, internal)".
Happens both if in front, or if it is on the backstack.
1.) add input text
2.) put app in background
3.)
adb -s 04UAY1WGLN shell am kill com.turo.nibel.sample
(this is my device id with the
-s
yours might differ or you might not even need it)4.) open app from launcher
App should be exactly as before, but on "First Screen" the text input is lost.
The text was updated successfully, but these errors were encountered: