Just thought I'd let you all know that I have just updated my Exception
Logger to Version 2 (0.9.5 RC1).
I fixed a bunch of bugs related to my converting it from my own use to
something that almost any developer can use :). I've also updated the
documentation considerably. YuviDroid helped
Ok... I said I would have this ready by the end of the weekend, and it
might still be the weekend somewhere :). Sleep got in the way of
finishing it last night.
I have just packaged the API and uploaded it to my server. You can
either download just the documentation or the entire .zip file
This is a bit long winded (sorry, but I need to explain what I'm doing
before I can ask the question).
Just wondering if I could get a few (hopefully few hundred) opinions on
this :
I developed an Exception Handler for my first Android app (released the
first month the market opened),
I have thought along similar lines. I think it should just be option a.
Don't confuse the user with options. In fact don't even allow user to reply
back directly.
On Sep 18, 2010 1:19 PM, Brad Gies rbg...@gmail.com wrote:
This is a bit long winded (sorry, but I need to explain what I'm doing
I believe option A is the best.
One thing you might consider as a premium option for developers is reporting
showing which crashes are more prevalent than others. I know Microsoft does
this internally for application crashes reported via Watson.
--Sean
Calendar:
If enough other devs do use it, I would put some effort into producing
reports to make it more useful, but one option that I will do
immediately is to put a button on the form listing your last ??
exceptions to download it in a comma delimited format so you can import
it into a spreadsheet
6 matches
Mail list logo
