Android — Content Providers + Dependency Injection (Dagger 2)

Are you an Android Developer? Do you use Dagger for Dependency Injection? Do you need to implement a Content Provider and don’t want to create a Singleton?
Well, that was my situation a few days ago and I didn’t have any idea on how to do so.

My “How can I do it?” reaction

The project that I worked on consisted on a VoIP mock application, using the phone contacts requested by a CursorLoader and allowing the user to make a “call” to a contact by clicking them. So, I used a ContentProvider and SQLite scripts to store these fake calls on database (Yeah, I know that I could store it using Room, Realm, GreenDAO etc, but I wanted to make it using SQLite). You may check the project here

The point is, how can I create a ContentProvider in a dependency Injection context? How can I provide a database instance to my ContentProvider? The answer is simple… Dagger 2.

Dagger has some new amazing features that can help us. These features include the power to allow you inject dependencies into Services, BroadcastReceivers and ContentProviders without making a reference to it in your application Component. You may find these new types described here:

My “Is that possible?” reaction

Ok, let’s show some code now. What are the steps that I need to implement it?

First, you need to include Dagger Android dependency in your gradle file

Second, it’s time to implements the interface HasContentProviderInjector in your custom application class. It will return an instance of an AndroidInjector based on ContentProvider type.

PS: Note that I called my injection method into attachBaseContext method, because the Provider onCreate method is called before Application onCreate and I got this by this StackOverflow post:

Third and finally you just have to inject the database into your ContentProvider class by doing:

Afterwards, you’ll be fine to use your databaseHelper instance along your ContentProvider class.

Woooow! We did it!

I hope it helped anyone that is reading and if you have any suggestion about this post, just tell me. Maybe there are better ways to solve this.

Thanks to Mick ( for the answer on StackOverflow and LeEnot ( for the answer on

Android Engineer @Triller