Adium

Ticket #1540 (new task)

Opened 3 years ago

Last modified 8 months ago

Update the crash reporter

Reported by: catfish_man Assigned to: bgannin
Priority: normal Milestone: Good idea for "later"
Component: Adium Core Version:
Severity: normal Keywords:
Cc: Patch:
Pending:

Description (Last modified by tick)

Review and update our built in crash reporter.

Change History

09/09/2005 02:14:34 AM changed by catfish_man

  • milestone changed from Adium X 0.90 to Sometime after 1.0.

Sigh... 10.4+ only. Milestone -> Future

09/10/2005 12:42:18 PM changed by evands

And we only get crash reports from people who have Unsanity's thing installed? What does this gain us?

09/10/2005 03:25:57 PM changed by catfish_man

It works similarly to Growl-WithInstaller.framework. There is a bit of an issue with people not trusting Unsanity products, however; they might get annoyed at us if we installed one.

10/29/2005 09:05:53 AM changed by wootest

Pros of the Adium Crash Reporter:

  • Fields for email and IM handle.
  • "Our own" web UI
  • We get crashes even if the user hasn't got admin privileges (needed to install SCR)
  • Duck. :)

Pros of Smart Crash Reports:

  • Works with other apps (dubious pro in that it doesn't benefit Adium)
  • Also submits to Apple

I don't know if the ACR submits to Apple as well - if it does or we can make it do that (manually or automatically) then there will, short of 'less code', effectively be no reason to switch systems.

10/29/2005 12:13:48 PM changed by zacw

SCR requires you to install its program. I for one will delete it if Adium tries to sneak it in. :) Iser came up with a nice solution, which he hasn't (or won't?) commit: the crash is sent when adium starts with no contact info, just "wanna help us out, yo?" with the default button to send (since people don't read dialogs, we'll probably get more).

10/29/2005 03:53:58 PM changed by catfish_man

""Our own" web UI" <-- This is not a 'pro'

10/30/2005 06:37:16 AM changed by wootest

catfish_man: Fair enough. It's certainly more to maintain, but it also means that we can make it do pretty much what we want, even if SCR is fairly great from what I've seen. If it's not a pro, it's not a con either (it can go either way).

I think the solution described by zacw in combination with a disclosure button for the how-did-this-happen and contact fields would work better.

10/30/2005 02:35:15 PM changed by catfish_man

So since it's a moot point right now, what can we do to turn our own system into more of a pro? Can we get a nice graph of crash reports per day? Can we get it moved to a faster server? Either of those would immensely enhance its usefulness. Some sort of data mining thing to find related crashes would be awesome, but that's a bit impractical, I think.

04/26/2006 11:18:00 PM changed by tick

  • owner changed from nobody to bgannin.
  • milestone changed from Sometime after 1.0 to Adium X 1.0.
  • summary changed from Switch to Unsanity's Smart Crash Reports to Update the crash reporter.
  • description changed.
  • field_haspatch changed.

SCR has been deemed a bad option to use. Updating the summary and description regarding this.

Brian, can you check this out after your prefs review?

I don't want this blocking 1.0 beta, but it would be good to get it at least somewhat ui reviewed before 1.0 is released. Push to 1.1 after that.

04/27/2006 05:00:06 PM changed by catfish_man

  • milestone changed from Adium X 1.0 to Adium X 1.1.

No, we need to get tickets off 1.0.

07/29/2006 08:08:59 AM changed by tick

  • milestone changed from Adium X 1.1 to Sometime after 1.0.

As well as 1.1. Someone will have to review the crash reporter UI of their own volition, unless this is assigned as a blocker to some future release.

05/15/2008 08:38:00 AM changed by djmori