There is no such call back on a production device for the Application class. The things you want to do should usually be done right after the changes are made, or in the onPause() of the respective app component.
The call to onActivityResult happens before onResume, actually (see the docs). Are you sure you’re actually starting the activity you wanted with startActivityForResult and that you’re setting the result of the invoked activity to RESULT_OK before returning a value to your activity? Try just putting a Log statement in your onActivityResult to log that value … Read more
Are ViewModels independent of activity/fragment lifecycles or just their configuration changes. ViewModels (VMs) are independent of configuration changes and are cleared when activity/fragment is destroyed. Following is the lifecycle of ViewModel from official site: Can the viewModel be shared with another Activity ? You shouldn’t do that with Activities. However fragments can share a ViewModel … Read more
I have found one way to do this….. Make one service like this public class OnClearFromRecentService extends Service { @Override public IBinder onBind(Intent intent) { return null; } @Override public int onStartCommand(Intent intent, int flags, int startId) { Log.d(“ClearFromRecentService”, “Service Started”); return START_NOT_STICKY; } @Override public void onDestroy() { super.onDestroy(); Log.d(“ClearFromRecentService”, “Service Destroyed”); } @Override … Read more
Any Activity that restarts has its onResume() method executed first. To use this method, do this: @Override public void onResume(){ super.onResume(); // put your code here… }
Destroying the instance specific resources first, before destroying superclass resources that the instance specific resources may depend upon makes sense, not the other way round. But the comments suggest otherwise. What am I missing? In my opinion: not a single thing. This answer from Mark (aka CommonsWare on SO) sheds light on the issue: Link … Read more
This happens when we try to add same fragment or DialogFragment twice before dismissing, just call if(mFragment.isAdded()) { return; //or return false/true, based on where you are calling from } Having said that, I don’t see any reason why to remove old fragment and add the same fragment again since we can update the UI/data … Read more
The main reason to use Fragments are for the backstack and lifecycle features. Otherwise, custom views are more light weight and simpler to implement. At first, I actually tried to build a phone/tablet app using custom views. Everything appeared to work across phones AND tablets, even switching from single panel to split panel. Where I … Read more
Lets start with a bit of background: What happens when you start an application? The OS starts a process and assigns it a unique process id and allocates a process table.A process start an instance of DVM(Dalvik VM); Each application runs inside a DVM. A DVM manages class loading unloading, instance lifecycle, GC etc. Lifetime … Read more
Per the documentation: void onRestoreInstanceState (Bundle savedInstanceState) This method is called between onStart() and onPostCreate(Bundle). void onSaveInstanceState (Bundle outState) If called, this method will occur after onStop() for applications targeting platforms starting with Build.VERSION_CODES.P. For applications targeting earlier platform versions this method will occur before onStop() and there are no guarantees about whether it will … Read more