Date: Tue, 11 Oct 2011 04:53:46 -0700 (PDT)
From: kaciula <catalin.moro...@gmail.com>
Reply-To: android-developers@googlegroups.com
To: android-developers@googlegroups.com
Message-ID: <7667531.600.1318334026769.JavaMail.geo-discussion-forums@vbbek10>
In-Reply-To: <7619709.586.1317994154884.JavaMail.geo-discussion-forums@yqmn40>
References: <7619709.586.1317994154884.JavaMail.geo-discussion-forums@yqmn40>
Subject: Re: Scenario where initLoader() does not call onLoadFinished()
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_598_11497953.1318334026768"

------=_Part_598_11497953.1318334026768
Content-Type: multipart/alternative; 
	boundary="----=_Part_599_6123586.1318334026768"

------=_Part_599_6123586.1318334026768
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

I noticed that this problem doesn't appear if I use a ListFragment with a 
CursorLoader/AsyncTaskLoader and setRetainInstance(true). It only happens 
when I use a basic Fragment with CursorLoader/AsyncTaskLoader and 
setRetainInstance(true).
------=_Part_599_6123586.1318334026768
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

I noticed that this problem doesn't appear if I use a ListFragment with a CursorLoader/AsyncTaskLoader and setRetainInstance(true). It only happens when I use a basic Fragment with CursorLoader/AsyncTaskLoader and setRetainInstance(true).
------=_Part_599_6123586.1318334026768--

------=_Part_598_11497953.1318334026768--