Thanks to all the tips, particular Jason who managed to send me a
stack trace which pin pointed the issue to the camera. I have a fix
in place now and comments from Droid users on the market indicate that
is it working for them.
Thanks everyone,
Mike
On Jan 9, 7:54 am, Sena Gbeckor-Kove
If you implement Flurry analytics you can see remote Exceptions by device and
location.
S
---
Sena Gbeckor-Kove
CTO/Founder - imKon
UK : +44 7788 146652
NL : +31 62 434 1290
s...@imkon.com|www.imkon.com
Asia (Singapore) :
35 Selegie Road, #09-14/15 Parklane Shopping Mall, 188307
Hi Dianne,
That's the difficulty, only end-users see the crash so I can't see the
stack trace. If I had my own Droid to try it on, it should be
relatively easy to work through the bug. Unfortunately, I don't have
a Droid and even if I wanted one, they are not available in my
country.
The app
The best bet for developers who cannot afford to buy all popular/
latest phones is to upload the stacktrace from the user's phone when a
crash occurs. See
http://stackoverflow.com/questions/601503/how-do-i-obtain-crash-data-from-my-android-application
for a lead.
I develop on ADP1 and had many
Do you specify a target SDK in your manifest? Do you use any Droid
specific layouts?
What firmwares do you support?
You can throw giant try catches around problematic code, log the
exception to local file, and upload them to your servers. Although
you might want to warn users you do this in
there's a Droid user sitting right here, i will try to get him to
install the app and log the crash to my ddms. then i'll send it on.
At 1:34 PM -0800 1/8/10, Matt Kanninen wrote:
Do you specify a target SDK in your manifest? Do you use any Droid
specific layouts?
What firmwares do you
6 matches
Mail list logo
