title: How is a running IntentService managed after the app process is killed
body: <p>Just trying to clarify my understanding of how an <code>IntentService</code> is managed by the OS once <em>terminating</em> states have been reached. By <em>terminating</em>, I mean when the current activity is destroyed or the app process is killed, as per the following documentation:
  <a href="https://developer.android.com/guide/components/activities/activity-lifecycle" rel="nofollow noreferrer">https://developer.android.com/guide/components/activities/activity-lifecycle</a></p>
  
  <p>Given the comment </p>
  
  <blockquote>
    <p>Also, an IntentService isn't affected by most user interface lifecycle events, so it continues to run in circumstances that would shut down an AsyncTask</p>
  </blockquote>
  
  <p>at <a href="https://developer.android.com/training/run-background-service/create-service" rel="nofollow noreferrer">https://developer.android.com/training/run-background-service/create-service</a>;</p>
  
  <p>I feel as if:<br/>
  1) A started <code>IntentService</code> is unaffected by the activity lifecycle. Is this correct?</p>
  
  <p>2) If (1) is true, will it continue to run indefinitely even after a terminating state is reached, up to some point that it either stops itself or the OS decides to stop it?</p>
  
  <p>In my particular situation, I'm using an <code>IntentService</code> during app startup to query APIs, grab content, and then add a new (landing) <code>Page</code> to the Xamarin.Forms navigation stack (this would be equivalent to starting a new activity).
  This leads me to my next question...</p>
  
  <p>3) What happens if the app is already in a terminated state when it comes time to the <code>IntentService</code> creating a new Activity? Surely the Activity can't be added to the navigation stack as it no longer exists once the app is terminated?</p>