onLoadFinished() called twice about adp-applistloader

[alexjlockwood]

No problem! I'm not sure if this is a bug in the tutorial or the framework implementation... it seems like a lot of people have the same issue and that it is more likely a problem with the framework though. Have you tried Google searching "onLoadFinished called twice"?

[feresr]

I have, and doing the following works!

"You can put the initLoader() method inside your Fragment's onResume() callback; then the Loader's onLoadFinished() will not be called twice anymore."

I have no idea why though. It should behave the same. It must have something to do with the way the loader manager works behind the curtains.

Anyways, thanks for your reply and for this example

http://stackoverflow.com/questions/11293441/android-loadercallbacks-onloadfinished-called-twice

[alexjlockwood]

Hmm... all of the documentation (and the Google I/O source code) call initLoader() inside the Activity/Fragment's onCreate() method, so I'm not sure what's going on there. Glad you figured out a solution though! In the sample app's case, whether or not onLoadFinished() is called twice doesn't really matter (I imagine the first time the method is called is when the loader is first initialized with null data and the second time is when the loader receives the asynchronously loaded data from the AsyncTaskLoader).

[o-nos]

Super! Thank you a lot.
I haven't found any solution for a bug on stackovewflow and tried your both variants. For me Alexs' one with fragents' onCreate() method helped.