Restoring State after Process Death (Do I need to care about process death?) 

It might not be easy to get your app into process death "naturally" but it will eventually happen so the question if you should handle it or not is not really there

Mitch, you have a talent to explain a complicated things in a simple way. Thank you! I love your courses!!!

I recently found your channel and there is so much to discover and learn ! Thanks and congratulation for the content !

Nice to see that you have the same opinion my team arrived at when we considered process handling for our production app!

Thanks for great content Mitch. The project that i work on is one of those project that handling process death really matters, we are facing big issues due to not properly handling process death, this content is going to be useful.

great content mitch. love it

You can now retrieve an instance of your ViewModel without any additional configuration (without Hilt for example). The default ViewModel factory now provides the appropriate SavedStateHandle to your ViewModel so you don't neccesarily need a special factory for it

Hey Mitch...you are just awesome....

Thanks mitch anther great video.

Thank you mitch

awesome stuff

Great video as always firstly :) The thing I wanna ask is are there any differences in process death when did by the OS ( low on memory so OS kills the app ) and when it is done manually through Android studio? What it did to me was when I terminated the process through Android studio it restored my last activity I was in before it went background and got killed , and when the OS killed the app it got restarted completely from the launcher activity. I can't find many resources online about this differences as mostly people point to the first case but not to the second. Can it be specific to device or manufacturer? I am running android 9, SDK 28 on Huawei honor lite 9 if it is of help to anyone with similiar situation :)

Great Journey!

Mitch, thanks

Great content, thank you. I have a question: why do you use setter functions instead of kotlin properties (overriding set for vars)? Just a habit from java or is there a specific reason? Thanks once again!

I have a question Mitch, How do you make Overnight blueberry French Toast, and also Cinnamon Toast?

you are genius 😍😍

Nice tutorial, Mitch! I have a question: what if I have opened 3 activities before the Process Death, for example. How can I re-open the last activity that the user was navigating?

thank you

Mitch, if we were to cache results from the API into Room, then how to check how many results are already cached and which one's need to be loaded for the first time? Assuming that the API is not going to update it's contents frequently, Is checking the query parameters of the request that the user about to make a good approach?

I dunno I have 4 GB RAM and when I could still visit places with food in them, just the camera then Google Maps were enough to get process death to happen 🤔 Anyway, overall good advice because process death IS important 😉 you can reduce the amount of code you wrote to make it happen with SavedStateHandle.getLiveData

Hi, here is my engement. The Assisted constructor have problem in newer version. @HiltViewModel class RecipeListViewModel @Inject constructor( private val randomString: String, private val repository: RecipeRepository, @Named("auth_token") private val token: String, @Assisted private val savedStateHandle: SavedStateHandle, ) required AssistedInject annotation in constructor, after applied it, my others DI asking for Inject annotation in constructor. Any idea, sir ? thank you

We can do it via Android studio. In Logcat there is red button for running app, when you hover its says "Terminate Application" 😉

Nice

gonna have some rice probably for lunch, awesome job

hey Mitch, here's your engagement:)

Random engagement!!!! And I had a capuccino for breakfast XD

Engagement Thanks

in the newer ver. of Hilt no need for @Assisted !

This was difficult

the phone not running linux operating system and Android is not top of linux kernel

restore engagement state

My engagement : it's very hot in siberia today )))

Now the rain is over. I'm eating a burger. Engaged from Colombo, Sri Lanka

engagement💍💍💍

I ate macaroni for breakfast, it was delicious.

buns💍💍💍💍💍💍

i ate nothing for breakfast

I don't like the use of Hilt in your guides. Hilt integration should be separate. It's impossible to learn the underpinnings of SavedStateHandle from this video because it presupposes use of an injection framework. Introducing frameworks makes the learning curve higher. While your code might be simpler, you ask a newb to take it on faith that it works without explaining it. "It's just magic" is not teaching.