Skip to content
New issue

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

"First Screen (type.fragment, internal)" loses text input after process death #2

Open
Zhuinden opened this issue Jul 27, 2023 · 1 comment

Comments

@Zhuinden
Copy link

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.
Screenshot_20230727-213335
Screenshot_20230727-213307

@Morfly
Copy link
Contributor

Morfly commented Jul 27, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants