I have had the same problem... It's not the Exception that is null, it's
that getMessage() returns null.
In some catch blocks (I think mainly or only to do with HTTPClient, but
it may happen also with JSON Exceptions... I can't remember) calling
e.getMessage() returns null since I updated my SDK to 2.2, and it caused
major issues because I normally wrote that to a log file, which meant
that my catch block was creating an exception....
Would love to know the reason... And would be even better if it got fixed.
In the meantime, I'm doing this in my catch block if I use the message
for ANYTHING:
String message = ex.getMessage();
if (message == null)
message = "null";
Then I write the message... It's a major pain...
I don't have an answer for you either... just letting you know it's not
just you :)
Sincerely,
Brad Gies
-----------------------------------------------------------------------
Bistro Bot - Bistro Blurb
http://bgies.com http://nocrappyapps.com
http://bistroblurb.com http://forcethetruth.com
http://ihottonight.com
-----------------------------------------------------------------------
Everything in moderation, including abstinence (paraphrased)
Every person is born with a brain... Those who use it well are the successful
happy ones - Brad Gies
Adversity can make or break you... It's your choice... Choose wisely - Brad Gies
Never doubt that a small group of thoughtful, committed people can
change the world. Indeed. It is the only thing that ever has - Margaret Mead
On 19/10/2010 9:35 PM, Johnny Molina wrote:
Hello,
I have recently hit a snag using the Android plugin to Eclipse. For
some reason, ALL of my errors being thrown don't initialize and show
me the error. Has anyone ever seen this issue before and if so, what
did you do to correct it?
In particular, I am seeing it when I try to invoke the HTTPGet in a
HTTPClient object. If I have no connectivity, then I should get an
error. The Catch block does fire when this occurs...however, when I
check my general Exception object, the object is NULL (NULL Pointer).
Why would this happen if the catch is grabbing the exception?
My exceptions used to be working....and I was able to see the stack
trace. However, I can no longer see any stack trace regardless of the
Exception class I am using. Can someone please help me understand what
the heck is wrong with Eclipse, Android, or both? Is there something I
am missing on the configuration side?...is this a bug?
Mind you, I have already used Stack Overflow for this question. It has
been viewed 40 times but no answer yet. I hope anybody on here can
help me understand why this is occurring.
Thanks in advance,
John
--
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
