Chris,
I've had a solution that I've been using in my apps for some time now,
and I'm working on reorganizing it so I can share it with other
developers. I've also partially solved the problem of not having any
contact info for the user. My solution is not perfect, but it's
certainly much better than not having it. I'm planning on making it
available to some developers for Beta testing in 2-3 days, and it will
include a way to view the exceptions, the user contact info, and (soon)
download them in a spreadsheet format, or just click a link and having a
(mostly) composed email popup so the developer can edit it and send it
without having to compose the entire email manually.
I'm almost 100% finished testing it, and I just have to finish some
documentation, and finish a little website work to support it well.
When I'm done, I will announce it on this list (by the end of this
weekend).
I do agree that I'd rather the framework did this for us, but my thought
on releasing my solution is that I could contribute it to the framework
sometime in the future when it's proven it's usefulness. I do also have
plans to open source the code when I have the time to do it. For now, it
will be something like the BUMP API where you copy a couple of files
into your project, and include a .jar file.
I'll let you know when it's ready.
Sincerely,
Brad Gies
-----------------------------------------------------------------------
Bistro Bot - Bistro Blurb
http://bgies.com
http://bistroblurb.com
http://ihottonight.com
http://forcethetruth.com
-----------------------------------------------------------------------
Everything in moderation, including abstinence
Never doubt that a small group of thoughtful, committed people can
change the world. Indeed. It is the only thing that ever has - Margaret Mead
On 16/09/2010 1:11 AM, Chris Stratton wrote:
I was thinking it might be useful if the platform let an activity
either programmatically or in the application manifest register an
intent that would be fired if the activity crashes due to an error,
force closes, etc.
This could either launch a simpler help activity in the apk (which
might attempt to determine device type /version to report), or simply
launch the browser to go to the developer's support / bug report
page. Either way, it would be better than all the "force closes on x"
observations cluttering up market comments. (In neither case could
the intent exceed the permissions of the activity registering it)
Yes, there are some possibilities to find things left behind on the
next run and realize a problem occurred - but a more built-in method
for getting users practically in touch with support would seem
beneficial.
--
You received this message because you are subscribed to the Google Groups "Android
Discuss" 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-discuss?hl=en.
