I don't see an answer to this in the Service documentation. It appears that activity manager reports the status of the service as started immediately after the call to startService(). So even if the creation or starting of the service (if not created or started) is async, the status change appears to be immediate.
I would guess then, from my scenario above, that onDestroy() would never be called after unbindService() ... since the activity manager sees the state as started already, even if onStartCommand() has not completed yet. On Nov 29, 2:09 pm, Streets Of Boston <[email protected]> wrote: > There is a whole lot to Services and the different ways it behaves when > using 'bind' vs 'startService' (and the the return-value of the Service's > onStartCommand callback). > It would be too much to describe right here. Try > this:http://developer.android.com/reference/android/app/Service.html -- 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
