In my spare time, I’ve been playing around with learning how to develop native apps for android devices. It’s all brand new to me and my general way of thinking for developing web applications has to change significantly.
One of the most annoying things to date has been debugging. I’ve been using Eclipse as my tool of choice for developing the android apps, which is an excellent piece of software. Before launching your app in the android emulator, it let’s you know if you’ve got syntax errors, missing files or pretty much anything it can spot.
But there are things it doesn’t spot. And when you launch the app in the emulator and get the dreaded “The application …. has stopped unexpectedly. Please try again. Force Close” error message, it’s hard to find information on where to look to find out what has gone wrong.
With a bit of research I was able to find out that there is a logging system that should be built into your environment, if of course you have that set up correctly. Simply open a command prompt and type “adb logcat”, hit return and happy days. You’ll have access to logs that should tell you exactly what is going wrong with your android app.
Now that I know how to do that, I can now move on and find the next hurdle I must overcome!
- Install Android market on Android emulator. Try out Android apps from PC. (varunkumar.me)
- Android/iPhone/BlackBerry/Nokia – Which platform(s) should developers target (punetech.com)
- Comparing the iPhone and Android Development Environments (raptureinvenice.com)
- Is it hard to become an Android developer…? (kreci.net)
- Logging the Android Way (mobilebytes.wordpress.com)
- Is Android an Ugly Platform? [Android] (gizmodo.com)