Alan Cassar wrote: > Can't connectivity be lost between calls though? I think the best bet is > using try and catch
The OP needs try/catch, to be certain. I held that truth to be self-evident. ;-) However, there is merit in determining at a point in time whether Internet connectivity exists. For example, you might disable menu choices that imply the use of a connection. In this case, I assumed he wanted those connectivity methods as part of his diagnostics, to confirm his suspicion that the device indeed had no connectivity at the time of the crashes. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Need help for your Android OSS project? http://wiki.andmob.org/hado --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Beginners" 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-beginners?hl=en -~----------~----~----~----~------~----~------~--~---
