On Apr 28, 12:39 pm, TreKing treking...@gmail.com wrote:
Then don't show the exception message. What will the average do with that?
If you know what the exception is and know what it means for you app, then
show them a dedicated message for that error. IOW, instead of showing
SocketException:
On Fri, Apr 29, 2011 at 9:36 AM, Guilherme Matsumoto
guih.matsum...@gmail.com wrote:
Thanks for the answer but the problem is that I have 2 different messages
for the same exception
Are you sure it's always the same exception? SocketException has a few
derived classes.
Also, there are ways
IIRC, Network unreachable is a NoRouteToHostException.
If that's the case, you can have a separate catch block for that.
-- Kostya
29.04.2011 18:36, Guilherme Matsumoto пишет:
On Apr 28, 12:39 pm, TreKingtreking...@gmail.com wrote:
Then don't show the exception message. What will the
Use different catch for each exception type or analyse message text sting.
--
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
Do your users care whether it is a 'time-out exception' or a 'network
unreachable'?
In either case, the server cannot be reached successfully. Both exceptions
are problems that cannot be solved directly by the user. What would the user
do differently when (s)he sees 'Time-out exception' or when
Base your response on the class of the message
(e.getClass().getName(), or e instanceof SomeClass).
On Apr 26, 2:56 pm, Guilherme Matsumoto guih.matsum...@gmail.com
wrote:
Hi Everyone,
Here is an example of my problem:
try {
// code that throws an exception} catch (Exception e) {
6 matches
Mail list logo
