As I said at http://community.logos.com/forums/p/82138/583394.aspx#583394 I'm still seeing crashes and warning messages that were supposed to be fixed.
Here's an example of the latter. I did a perfectly normal 'Quit' of the program -- no sign that it was crashing -- but the next time I open I get a "Logos quit unexpectedly" message.
Logs: 4621.LogosLogs.20140414-135508.zip
It looks like the "crash" log that was sent was an old one from 4-6-2014 when you were running 5.2a (5.2.1.0067).
Would you mind running the following command from Terminal and pasting the output here? (You'll need to make sure it's all on one line)
defaults read com.logos.Logos "CrashReportSender.lastCrashDate" && ls -lt ~/Library/Logs/DiagnosticReports/Logos_*.crash | head -n5
The last Logos crash report Apple created in DiagnosticReports is from that date. As you could see, the last in the Logos Logging folder is from yesterday, but 0 K (I'm pretty certain I didn't have any crash yesterday). None from today, when this 'unexpected quit' is supposed to have taken place.
Would you mind running the following command from Terminal and pasting the output here?
2014-04-13 21:38:25 +0200-rw-------@ 1 XX staff 99108 13 Apr 21:38 /Users/XX/Library/Logs/DiagnosticReports/Logos_2014-04-06-234152_XXs-Mac-mini.crash-rw-------@ 1 XX staff 111768 6 Apr 20:41 /Users/XX/Library/Logs/DiagnosticReports/Logos_2014-04-01-122259_XXs-Mac-mini.crashc193-14-20-23:~ XX$ (With a few letters changed to X's.)
Looks like that probably says the same as I just said above.[:)]
The problem is that the latest crash report file (Logos_2014-04-06-234152_XXs-Mac-mini.crash) was modifed on Apr 13 at 9:38 PM, which was after it was originally submitted. Currently, if a crash report is modified it will get resubmitted because the crash reporter looks for a more recently modified crash report than the last time it sent a report.
I'll file a bug to look into checking for the creation time, rather than the modification time.
