Call to main activity in onPostExecute (after activity is destroyed or in stopped state)

Question

In my application, I'm having an AsyncTask that uploads some data to the server and interacts with the calling activity using an interface "FetchCompleteListener " that I wrote.

The calling activity implements a FetchCompleteListener and passes its own instace to the AsyncTask.

The given AsyncTask calls FetchCOmpleetListener's onFetchCoMplete in onPostExecute()

My question is - what happens in the following scenarios:

When the given activity is in stopped state
When the given activity is finished/destroyed?

Is this a case of memory leak? Will my application crash when I try to call onFetchComplete in onPostExecute()?

You should use a bus... http://stackoverflow.com/questions/31499875/event-bus-fragment-unregister/31499998#31499998 — EpicPandaForce, Aug 08 '15 at 17:27

score 1 · Accepted Answer · answered Aug 09 '15 at 05:18

You should always decouple background tasks from your ui. you can do one of the following:

Your ui will register a broadcast receiver inside onResume (of course unregister that in onPause), the background task will send a broadcast that will be caught by the ui when it is active
You can queue up your result in some service classes (or what suits you best), when the corresponding ui comes alive it will take results from queue (based on some TAG)
you can use an EventBus like Otto or greenrobot

Thanks for the info. I've moved my code from AsyncTask to a Serive. — avin, Aug 16 '15 at 17:40

Call to main activity in onPostExecute (after activity is destroyed or in stopped state)

1 Answers1