Is the Application class guaranteed to be instantiated before a defined boot receiver is called

Question

Excuse me for such an elementary question. I understand that the Application class is instantiated when my app\'s process starts and I understand when the phone is complete

Answer 1

Phone reboots, phone starts all processes with BOOT_COMPLETED, phone fires off BOOT_COMPLETED broadcast.

I would phrase it more as "phone reboots, phone fires off BOOT_COMPLETED broadcast, and normal broadcast processing occurs, including starting any necessary processes".

My concern came from wondering if I reference Application class instance variables within my boot receiver if the receiver would ever get called before my Application class was instantiated.

It shouldn't. The order of instantiation is supposed to be:

• any ContentProviders you have defined in your manifest, then

• the Application instance, then

• the component that triggered the need for the process (in this case, your ACTION_BOOT_COMPLETED BroadcastReceiver)

Answer 2

An Application is always started before any of its Activities/Services/Receivers. Here are a couple of blogs that go into the details:

• http://multi-core-dump.blogspot.com/2010/04/android-application-launch.html
• http://multi-core-dump.blogspot.com/2010/04/android-application-launch-part-2.html

[Edited]

But, according to a comment by @CommansWare:

Based on logging, the instance of the ContentProvider is created after the instance of the Application. However, onCreate() of the ContentProvider is called before onCreate() of the Application.

So, it is probably not safe to try to use the Application instance within a provider's onCreate().