On Sun, Feb 3, 2013 at 12:48 PM, Jake Colman <[email protected]> wrote:
> Simple question: do I just ignore the intent since I can't do anything > with it anyway? > Am I supposed to know what to do with it? If not, why does Android bother > doing it? > That depends on your use case. Android restarts your Service if you request it to, so it's doing what you asked. However, I too, find it strange that it "loses" the Intent and sends null. But you can use this an indication that this restart happened. In this case, depending on what you wanted to do with the Service, you can rebuild the Intent yourself, re-schedule an alarm, or warn the user of some error state, etc. I generally just return in my case, but it's better to know that the Service was still called as expected even if the Intent was lost then not have the Service called at all. That would probably cause more problems for developers. ------------------------------------------------------------------------------------------------- TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago transit tracking app for Android-powered devices -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
