What I usually do is adding app-internal logging all over the place. The log lines go into a text file, so you don't depend on the system log and don't need to fluff up your app with another really sensitive permission.
For covering crashes you can set a custom UncaughtExceptionHandler<http://docs.oracle.com/javase/1.5.0/docs/api/java/lang/Thread.html#setDefaultUncaughtExceptionHandler%28java.lang.Thread.UncaughtExceptionHandler%29>for logging the stack trace. Make sure to use the default uncaught exception handler for processing that exception (or at least kill the app process), otherwise your app thinks that everything is alright. On Monday, July 9, 2012 6:03:18 PM UTC-5, [email protected] wrote: > > No, I don't. Is there an easy way to gather this information from a > user? I can put some debug code on this user's machine. > > > > On Mon, Jul 9, 2012 at 11:14 AM, Justin Anderson <[email protected]> > wrote: > > Do you have access to the stacktrace? > > > > Thanks, > > Justin Anderson > > MagouyaWare Developer > > http://sites.google.com/site/magouyaware > > > > > > > > On Sun, Jul 8, 2012 at 12:03 AM, [email protected] <[email protected]> > > wrote: > >> > >> We have an app on the market for a while now, mostly it works great. > But > >> recently we got a couple report that it force closes on some devices, > since > >> we don't have those devices to debug the problem, I hope I can ask the > >> question here and maybe someone can share some lights about what we > should > >> do. > >> > >> The basic problem is that we have an activity A, which has a button for > >> people to configure some information. So, we have an Activity B which > >> collects those information. So, user click the button and Activity B > will > >> pop up, after users finish the settings, they click finish button or > cancel > >> button there and Activity B closes and Activity A has a > "onActivityResult" > >> call which collect which button was clicked and will adjust some > >> information. But this force closes on some devices after user click > either > >> button. > >> > >> We added some debug code in "onActivityResult" but it finished the call > to > >> the end without crashing, so, we have no idea what other function > should be > >> called after that. We don't have onResume function in Activity A > because we > >> thought since we don't care about it, it should just use the default > >> implementation. And we do have onSaveInstanceState function. So, one > user > >> who has this problem is willing to test anything or we can add debug > code to > >> anywhere, but since onActivityResult returns okay, we have no idea what > to > >> do next. > >> > >> Any suggestions about how to figure this out without the actual device > to > >> hook up the debugger? > >> > >> Thanks > >> > >> -- > >> 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 > > > > > > -- > > 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 > -- 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
