Indeed, the loader manager destroy() method is called and the field mDestroyed is set to true. After this, the loader manager is not functional anymore. In onLoadComplete() it exits if mDestroyed is set to true. So i guess the problem is that the loader manager for that fragment is destroyed but our fragment is still alive. I would venture to say that this is a bug.
It would be helpful if we find a workaround. I have a big app with a lot of fragments using loaders. For some, I removed setRetainInstance(true) but for others I must use setRetainInstance(true). -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
