为什么 ContentProvider.onCreate() 在 Application.onCreate() 之前被调用？

Question

I registered a ContentProvider in AndroidManifest.xml, and the ContentProvider.onCreate() was called even before the Application.onCreate(). I don't understand this behavior, in my opinion, It's more natural that Application.onCreate() be called before any of the components in the application. Could someone tell me the timing of Application.onCreate() and other components' onCreate() gets called?

Answer 1

According a Google's issue it's how this should work (although documentation is wrong).

There's another question that have a workarround that can help you.

Answer 2

It is exactly how it should work.

Documentation of Application class was updated starting from Android 4.2 and it says that Application#onCreate()

Called when the application is starting, before any activity, service, or receiver objects (excluding content providers) have been created.

Answer 3

When an Android app process is first started, there is well-defined order of operations:

1. Each ContentProvider declared in the manifest is created, in priority order .
2. The Application class (or custom subclass) is created.
3. If another component that was invoked via some Intent, that is created.

Please read more: https://firebase.googleblog.com/2016/12/how-does-firebase-initialize-on-android.html