On Thu, Dec 27, 2012 at 12:22 PM, Jake Colman <col...@ppllc.com> wrote: > Hmmmm. The service's onHandleIntent is basically a set of 'if/else' > clauses for the intents I am looking for with a final 'else' for any > unrecognized intent. After that final 'else' there is no other code.
Which means your service will be destroyed a handful of microseconds after that final else. Using an IntentService for location tracking is a no-no. > In my logcat I see that the code for determining the location has been > triggered (I have debug statements showing me the available and best > providers) but then I immediately see the service's onDestroy method > logging that it was called. That is precisely what I am telling you is supposed to happen. > Either way, how do I make sure I stay > alive long enough for my Listener to get an update? Stop using an IntentService. Use a regular Service, one for which you control the lifecycle. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Localized Android Question-and-Answer Sites: http://www.andglobe.com -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
