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
Doc update: testing tombstoning and why it's important #4552
base: develop
Are you sure you want to change the base?
Conversation
I'm shedding some light on tombstoning and why it is important. I'm also demonstrating how to test it on Android.
Sounds overengineered for testing. Have you tried enabling "Don't keep activities" in Developer options on Android? |
Yes I have tried it and it doesn't work, meaning Also there is another issue with Don't keep activities setting, you look at your app in a way almost no (if any) users sees it. Issue #3584 is an example of this functionality being not very well understood. |
I see. I use single Activity with multiple Fragments so it worked well in my case and restored all the Fragments correctly. |
I'm shedding some light on tombstoning and why it is important. I'm also demonstrating how to test it on Android.
✨ What kind of change does this PR introduce? (Bug fix, feature, docs update...)
docs update
no details about how to test tombstoning
🆕 What is the new behavior (if this is a feature change)?
added description detailing why implementing tombstoning is important and how to test it
💥 Does this PR introduce a breaking change?
no
🐛 Recommendations for testing
no
📝 Links to relevant issues/docs
nothing
🤔 Checklist before submitting