Before you go through the exercise of rooting the device etc., make sure you've verify that the new version of your app even runs on 1.5. I fell into that trap recently when I introduced a new, innocuous feature that relied on a piece of the SDK that wasn't available in 1.5. I never went back to test this on 1.5 (emulator) until a user brought it to my attention. Confusion for a while until I figured it out. I pull stack traces remotely, but what happens is that the app will not even launch, i.e. any method to pull a stack trace from within the app will not catch the problem.
On Jun 14, 3:16 pm, Brad <[email protected]> wrote: > Hi, > > I have a customer who upgraded his app (that I wrote and publish) and > now it's force closing immediately upon launch. There is critical > payroll data contained within the app so it's important that we are > able to recover the data. > > If I could see the output of the log (as from logcat), I'm sure I > could diagnose the problem, but the user is not technical and cannot > use a shell. Is there a way to access the user's log from within the > phone? Or can someone recommend a better approach? > > 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
