On Tuesday, June 25, 2013 11:04:42 AM UTC-7, a1 wrote: > > > Assuming you are doing all that and giving the best user friendly message >> to the user possible, you still might have a vested interest in the nitty >> gritty details of those exceptions to fix the problem. Original poster's >> query is very legitimate. >> > Why? How can you fix IOException? > >
If you believe that logcat logs are never helpful for tracking down issues, we can agree to disagree. You stated above that "most of the runtime exception indicate bugs in code." Are you to assume that a handled checked exception means that there aren't any bugs in the code? I don't, and that's why log messages can be helpful. An IOException isn't necessarily the end of the story. You could be not using the right timeouts, the right credentials, or the right format. The user could have problems with DNS. Could you retry more or less times? Could you do something different on the server, if you control it? Are there some changes on a server you do not control? Is the user choosing an invalid path or filename and are you letting them do that when you shouldn't? Nathan -- -- 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.
