Am Dienstag, 3. Dezember 2013 06:08:40 UTC+1 schrieb sree: > > how can i handle this problum and how can i avoid app force close problum. >
It is not *a* problem. If you have to ask on that general level it might be a multitude of problems all resulting from writing sloppy code. (Side-note: The fact that you did not use a spell checker for the posting to have «problum» corrected supports my assertion that you work sloppy) 1. You should check for Null Pointers. All IDEs have a system which uses @Nullable and @NotNull annotations to aid you in finding null pointer problems. USE IT. You can also find null pointer problms in the log-cat but proactive search is better. 2. You should check the log-cat for exceptions and handle them *appropriately*. That is don't fall for the Error hiding<http://en.wikipedia.org/wiki/Error_hiding> anti pattern. Martin. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
