Welcome to OStack Knowledge Sharing Community for programmer and developer-Open, Learning and Share
Welcome To Ask or Share your Answers For Others

Categories

0 votes
264 views
in Technique[技术] by (71.8m points)

android - Exception is always NULL

Why will the Android "Catch" handler not initialize an Exception object?

When an error occurs and my code is trying to initialize an Exception object it is always NULL.

The above doesn't make sense to me, because the exception should always initialize the Exception object - period. It should never be null if an error occurs.

I am fairly new to the Eclipse Android IDE/SDK, and I am sure I don't have everything set up 100%. However, this type of functionality would seem to me that it should work all the time, not after being set up.

See Question&Answers more detail:os

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome To Ask or Share your Answers For Others

1 Answer

0 votes
by (71.8m points)

One possible cause is that you are trying to make a network connection on your main thread, which works fine pre-2.3.3/Honeycomb (SDK level < 10 for example) but will be thrown as an

android.os.NetworkOnMainThreadException

since SDK level 10.

Check this: http://developer.android.com/reference/android/os/NetworkOnMainThreadException.html

The problem is that Eclipse doesn't really know about this exception (since it is conditionally thrown based on different SDK level so Eclipse probably can't get a correct instance of this exception, that explains why your exception object is always NULL)

Solution: create a separate thread or use AsyncTask to perform your network connection request.


与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome to OStack Knowledge Sharing Community for programmer and developer-Open, Learning and Share
Click Here to Ask a Question

...