[android-developers] Re: Scenario where initLoader() does not call onLoadFinished()

Hi Tobias I don't know enough about your specific problem, but I can only tell you that the solution that I documented further up is in use in my production applications without problem. The main difference I guess is that I do all loader stuff inside the fragments (i.e. the initloader code is

[android-developers] Re: Scenario where initLoader() does not call onLoadFinished()

Hello Rainer, currently struggling with the same issue and already tried nearly every possible solution out there (besides using the SupportLoaderManager) Your solution does not work in my case, after configuration change i still get no onLoadFinished-callback and therefore the data-field stays

[android-developers] flavoring a lib according to the main project(android - gradle)

hi. I have a library which is used by many applications in my company. This library basically handles commercials, backend comm and licensing. basically it supportd 3 buildTypes: release, debug and staging which is like debug only with buildConfigField that states it's staging build. the