5 ms·
Android Errors in Real Time
- barabeke 14y agogreat stuff!
- jmt7les 14y agoVery 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 14y agoYet at the same time a huge deal maker.
- lucian1900 14y agoIt's more a failing of mainstream programming languages having nulls.
- jmt7les 14y agoOh 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.
- lucian1900 14y agoThe alternative is the horribly restrictive iOS app store. As a user and as a developer, I prefer Play.
- quarterto 14y agoIt's staggering how many of these are NullPointerExceptions. Java needs nullable types.
- weakwire 14y ago+1
- j4_james 14y agoI 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.