There are parts of the application that are created prior to Application.onCreate being called: notably ContentProviders
The Application.onCreate documentation was changed recently: From: "Called when the application is starting, before any other application objects have been created." To: "Called when the application is starting, before any activity, service, or receiver objects have been created. Note that content providers are created before the application object (see http://code.google.com/p/android/issues/detail?id=8727)" It now explicitly mentions that 'receiver objects' are created prior to onCreate being called. So you should be okay, but good to check the source. Just as a sanity check, but you've included the Application in your manifest file? This would also prevent onCreate from being called. Good luck bud. On Jan 18, 6:26 pm, Kristopher Micinski <[email protected]> wrote: > Right..., but you shouldn't spawn a new process for each onReceieve... > > kris > > On Wed, Jan 18, 2012 at 1:21 PM, Streets Of Boston > > > > > > > > <[email protected]> wrote: > > Your Application.onCreate is called only once for each process it runs in. > > (if you have multiple processes for your app, the Application.onCreate is > > called multiple times, but still only once per process). > > > -- > > You received this message because you are subscribed to the Google > > Groups "Android Developers" group. > > To post to this group, send email to [email protected] > > To unsubscribe from this group, send email to > > [email protected] > > For more options, visit this group at > >http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
