Android Errors in Real Time

http://www.bugsense.com/live

by jonromero • 13 years ago

45 9 13 years ago

barabeke• 13 years ago

great stuff!

jmt7les2• 13 years ago

Very useful info, if it's accurate. Mostly nullPtr exceptions, signs of sloppy programming. One pitfall IMO of Android is how easy it is to push apps to the market.

scrapcode• 13 years ago

Yet at the same time a huge deal maker.

lucian19002• 13 years ago

It's more a failing of mainstream programming languages having nulls.

jmt7les2• 13 years ago

Oh totally agree, I just think more care could be taken since these are obvious issues, and have been for relative ages now. I just hate how easy it is to slap together an apk and throw it on the market, though Play Store's vastness is nice for the keen users.

quarterto• 13 years ago

It's staggering how many of these are NullPointerExceptions. Java needs nullable types.

weakwire• 13 years ago

j4_james• 13 years ago

I would have thought this is just because Java forces you to catch most exceptions. It's only the RuntimeException subclasses (which includes NullPointerException) that are unchecked. And a good deal of those are quite obscure. I really wouldn't expect to see many occurrences of FileSystemAlreadyExistsException or MalformedParameterizedTypeException.

There are also the Error classes (including OutOfMemoryError) that wouldn't automatically be caught, but there aren't many likely candidates there either.

Android Errors in Real Time

Related Stories