Skip to main content

Writing an Android library - Using its own custom Application class (getApplication)



I'm writing an Android library and I wish to use a custom Application class, which will be accessible from all of the library's activities (using the getApplication method).





The problem is when I call the getApplication method from one of my library's activities, it returns the application class of the app using my library (and not the custom class I declared in the library's Android manifest).





My current guess (based on this answer and the official documentation ) is that the application using my library must also declare the custom Application class in their Android manifest - which is a problematic solution, since that application can also have its own custom class (and a single app cannot have more than one custom Application class, right?).





Can anyone offer a better solution? (or verify that this solution is accurate)





Any help will be appreciated..


Comments

  1. Nothing wrong with your custom Application implementation and AndroidManifest.xml. The correct way of using your custom Application in code is casting.

    Suppose you have a MyApplication that extends android.app.Application, to get MyApplication instead of Application:

    Boolean runInTest = ((MyApplication) getApplication()).isRunInTet();


    Hope that helps.

    ReplyDelete

Post a Comment

Popular posts from this blog

Slow Android emulator

I have a 2.67 GHz Celeron processor, 1.21 GB of RAM on a x86 Windows XP Professional machine. My understanding is that the Android emulator should start fairly quickly on such a machine, but for me it does not. I have followed all instructions in setting up the IDE, SDKs, JDKs and such and have had some success in staring the emulator quickly but is very particulary. How can I, if possible, fix this problem?