catching null exception [duplicate]

Answer 1

The exception will never be null in that block. If the instruction pointer in the debugger is pointing at the catch line, you need to step one more line to get the exception to be accessible to you. You may want to add a line of code (potentially a log call) to your catch block and put your break point on that to catch what ex is.

Answer 2

I had exactly the same problem inside an AsyncTask, while debugging on a real device (Galaxy Tab 2). So I too can confirm, that this strange problem is real.

For me the accepted answer didn't help.

But in my case the problem mysteriously went away after unplugging the usb plug of the device and connecting it again afterwards (and then running my app again).

Answer 3

This sounds like the source code and the compiled classes are out of sync, so the debugger is stepping into the wrong block.

Try to do a clean and then a rebuild.

Answer 4

Add some log statements and check. Your ex may be out of scope.