On Mon, Jul 23, 2012 at 9:04 AM, Zoltán Páll <[email protected]> wrote: > 1) When running an app from Eclipse, the app might crash. Eclipse shows me a > stack trace (Debug panel) but it all looks like native Android functions, > which I have nothing to do with, so after playing around with Eclipse, I > found that if i step over the stops, LogCat will spit out a partial stack > trace. Is this the proper way of finding the faulty line of code? How do you > guys handle this?
I usually let the crash continue and examine LogCat. > 2) Also when crashing, my app might be crashing because of not having the > right permissions. (How) Can I find out what permissions stop the app from > running, or do I just have to guess that it needs some camera-related > permissions if the faulty lines proves to be related to camera? The stack trace will tell you when your problem is due to permissions -- the exception should tell you the permission that you need. Also, many (most?) methods in the Android SDK that require a permission are documented as such, either at the method or class level, in the JavaDocs. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 3.8 Available! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
