Built a similar solution a few months ago that integrates with Google
and Atlassian issue trackers. heroicefforts.github.com/Viable.
On May 20, 6:46 pm, Kevin Gaudin wrote:
> Hello Justin,
>
> handleException() handles your caught exceptions exactly the same way
> uncaught exceptions are handled
Same here. You don't expect the conference to sell out a month before
the earlybird ends. I like a good party, but I can't say that I'd buy
a trip across the country for happy hour...not on my dime.
On Mar 16, 4:46 pm, Robert Green wrote:
> Yes this is about Android development :)
>
> Well I've
The source and binaries of the prototype have been posted on Github
for any interested. Comments are welcome.
http://heroicefforts.github.com/Viable/intro.html
On Feb 25, 9:09 pm, laphroaig15 wrote:
> A follow up. I'm close to a working prototype as I described a few
> weeks ago
The source and binaries of the prototype have been posted on Github
for any interested. Comments are welcome.
http://heroicefforts.github.com/Viable/intro.html
On Mar 3, 2:29 am, laphroaig15 wrote:
> Dupes were a concern for me as well; not only on the receiving side,
> but also for b
ces;
>
> Of course, since the logs are not part of Android's official API, the
> result might be unreliable if not implemented correctly. But by
> analyzing existing platforms and applying some heuristics, I believe
> the result would be good enough for the majority of applications.
>
I've been working on a 3rd party application that uses meta-data and
exception handling as suggested above to allow users to submit this
data to a developer's issue tracker and to browse said tracker. I
plan to put it up on github next weekend. It's more of a prototype at
the moment, but I'm hopi
in a row.
http://tinyurl.com/yeol4sh
http://tinyurl.com/ybeqybd
regards,
Jess
On Feb 2, 7:36 pm, laphroaig15 wrote:
> It certainly wouldn't be closed. I'm not looking to implement yet
> another issue management system or sell a hosted solution. There are
> many folks who already do
ne as well. I've already built a registry now, but
I'm still curious.
thanks,
Jess
On Feb 24, 9:38 pm, Dianne Hackborn wrote:
> The data has the package name.
>
>
>
>
>
> On Wed, Feb 24, 2010 at 5:55 PM, laphroaig15 wrote:
> > It seems that the package rem
It seems that the package removed events are sent at the very end of
the process; after the package has been removed. It seems that all we
get to work with in this event is the uid. Is there a particular
reason that this is the case? Couldn't the application info be passed
with the event context
I ran into a lot of similar problems. Some notes for anyone seeking
to implement an authenticator.
Three details that I took away:
1. Your login activity has to invoke
AccountManager.addAccountExplicitly before the account is created
(even though the Android debug claims to have created it). I
ally, "whatever" cannot self-
reference its own automated exception reporting capabilities. ;)
thanks for the input,
-Jess
On Feb 15, 2:01 pm, Mark Murphy wrote:
> laphroaig15 wrote:
> > Is there some way to interact with the android packages to
> > retrieve a context in a stati
I'm trying to handle exceptions at a global level. My understanding
is that the only way to do this is with an UncaughtExceptionHandler.
However, this reduces one to the primitive java file and network i/o
packages. I'd like to be able to broadcast an intent or bind to a
service. Is there some w
me implement, a similar plugin for Google Issue
Tracker.
I appreciate the excellent input. I'll follow up when I have some
seed code to contribute.
-Jess
On Feb 1, 9:57 pm, theSmith wrote:
> On Feb 1, 4:52 pm, laphroaig15 wrote:
>
> > The alternatives you
Broadcast events would work to make it usable with several apps but
> I'm not sure how much information you can stuff into a broadcast...
> For example I would at least want a full stack trace and cause trace
> from the exception that occurred, and this can easily be 20+ lines.
>
I'd finished up my first android application, a simple power
management app, and was preparing to release it when I realized that I
didn't have a proper design or infrastructure for bug reporting. One
of my pet peeves with the applications on the Android marketplace is
that there's inadequate visi
15 matches
Mail list logo
