Skip to main content

Fragment LifeCycle

Normal setRetainInstance(true) Description
onAttach onAttach Called once the fragment is associated with its activity.
onCreate - Called to do initial creation of the fragment.
onCreateView onCreateView Creates and returns the view hierarchy associated with the fragment.
onActivityCreated onActivityCreated Tells the fragment that its activity has completed its own Activity.onCreate().
onViewStateRestored onViewStateRestored Tells the fragment that all of the saved state of its view hierarchy has been restored.
onStart onStart Makes the fragment visible to the user (based on its containing activity being started).
onResume onResume Makes the fragment begin interacting with the user (based on its containing activity being resumed). As a fragment is no longer being used, it goes through a reverse series of callbacks:
onPause onPause Fragment is no longer interacting with the user either because its activity is being paused or a fragment operation is modifying it in the activity.
onSaveInstance onSaveInstance Called to ask the fragment to save its current dynamic state, so it can later be reconstructed in a new instance of its process is restarted.
onStop onStop Fragment is no longer visible to the user either because its activity is being stopped or a fragment operation is modifying it in the activity.
onDestroyView onDestroyView Allows the fragment to clean up resources associated with its View.
onDestroy - Called to do final cleanup of the fragment's state.
onDetach onDetach Called immediately prior to the fragment no longer being associated with its activity.


Android's default behaviour when configuration changes
One of configuration changes to be able to test is device rotation. Android destroy and create again activity and it will affect the lifecycle of the activity. Android will restore layout when it recreate activity and fragment.

setRetainInstance
Control whether a fragment instance is retained across Activity re-creation (such as from a configuration change). This can only be used with fragments not in the back stack. If set, the fragment lifecycle will be slightly different when an activity is recreated: onCreate and onDestroy will not be called. Default value is false. One of practices for this option is to use Asynchronous operation.
Labels:

Comments

Post a Comment

Popular posts from this blog

Apply Kotlin DataBinding to Android Studio Generated Main Activity

I posted how to setup Kotlin and DataBinding in Android Stuido in the last blog (http://marksunghunpark.blogspot.com.au/2017/04/kotlin-binding-library-setup-in-android.html). In this post, I am going to how to use DataBiding in the MainActivity when you create a navigation drawer project from Android Studio templates. Layouts You will have four layouts in app/src/res/layout folder: app/src/main/res/layout/activity_main.xml app/src/main/res/layout/app_bar_main.xml app/src/main/res/layout/content_main.xml app/src/main/res/layout/nav_header_main.xml And activity_main.xml contains all other layout using include layout. You need to have tag in activity_main.xml , app_bar_main.xml and content_main.xml . If you don't have the tag, Binding library cannot recognise the sub layouts properly. Binding library doesn't support toolbar and navigation drawer yet, so you can use using BindingAdapter if you want to use binding library.(But I'm gong to skip this part for simplici...
Post a Comment
Read more

How to test AsyncTask in Android

In Android, test is not as easy as any other platform. Because Android test cannot be run without emulator. Particulary when it comes to AsyncTask or Service, it is difficult to test because they are different type of thread and hard to check their result. Then, how can we ensure the result of AsyncTask valid? AsyncTask is a thread and an asynchnorous as the name means. So, we need to wait for it finishes its job and need to capture the event. Then, when it happens in AsyncTask. It can be one of onBackground() and onPostExecute() methods. It doesn't matter you use onBackground() or onPostExecute() but I prefer onPostExecute(). Anyway, we can test an AsyncTask if we can hook it. Then, how can we hook it? For that, we can use callback pattern. But we need to delay main thread to wait for the AsyncTask's job done because we want to check the result. So the structure for the test would be like: 1. Create AsyncTask A 2. Injection a callback into A 3. Wait until A finish 4....
8 comments
Read more

How to setup Kotlin in Android Studio

Brief about Kotlin What I am impressed in Kotlin is Android Extensions. It enables you to remove boiler plate code of setting views. You have bind your view object by calling findViewbyId() but Kotlin supports it just importing kotlinx.android.synthetic. .* package. Let's have a look at an example: res/layout/login.xml LoginActivity.kt package com.ispark.kotlin.login import kotlinx.android.synthetic.login.* import android.os.Bundle import android.support.v7.app.AppCompatActivity import android.text.TextUtils import android.util.Log import android.widget.TextView import android.widget.Toast import com.ispark.kotlin.R import kotlin.String public class LoginActivity : AppCompatActivity() { private val LOG_TAG: kotlin.String = "LoginActivity" override fun onCreate(savedInstanceState : Bundle?) { super.onCreate(savedInstanceState) setContentView(R.layout.login) setTitle(R.string.pleaseSignIn) log...
Post a Comment
Read more