Mac Version - Quit Unexpected Message Ever Time - Seem to be from Last update?
This shows every time I start Logos. I believe it started happening with the last update???
Comments
-
same here.
0 -
I am updating a different machine to the latest... I'll post if the problem starts happening with the new bits on that machine also with the latest bits...
0 -
RandyM said:
This shows every time I start Logos. I believe it started happening with the last update???
Please enable and post logs. See my signature line for instructions.
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
-
I'm also getting this problem but can't post logs at the moment - away from home on unreliable connection.
Running Logos 6 Platinum and Logos Now on Surface Pro 4, 8 GB RAM, 256GB SSD, i5
0 -
Same here. It is getting aggravating to say the least. Trying to do some study tonight but with Logos crashing like crazy it is difficult. I have tried to attach log files to see if anyone can shed some light on what is going on. 6082.LogosLogs.aaronandlesliesimac.20150323-203855.zip
I have an iMac that is running 10.10.2. Logos 6.1 SR-3
0 -
RandyM said:
Logs attached
For clarification: Did you allow the app to crash AFTER you enabled logging but BEFORE you restarted the app? I don't see a crash in your logs.
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
Aaron Baldridge said:
Same here. It is getting aggravating to say the least. Trying to do some study tonight but with Logos crashing like crazy it is difficult.
Same as above: Did you allow the app to crash AFTER you enabled logging but BEFORE you restarted the app? I don't see a crash in your logs.
It really would be best to create a new thread.
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
Randy,
Can you please upload the crash report located at /Volumes/Data/Users/Randy/Library/Logs/DiagnosticReports/Logos_2015-03-23-154423_MacMini-2.crash so we can get more information about the issue you are having?
Thank you,
Martin
Mac Developer
Faithlife0 -
Yes i did - i enable logging started the app - then quit the app and started again. Each time i start the app it says it quit un expected.
Note: i dont see the app crash. The system just says it did everytime I start the app.
0 -
Aaron,
The last crash report I can see referenced in the logs you uploaded is from March 21st. Can you open Console and on the left under "User Diagnostic Reports" find the latest report for Logos and attach that crash report?
Thank you,
Martin
Mac Developer
Faithlife0 -
I uploaded the crash log.
I also threw app away and downloaded a fresh copy. I "think" it might have stopped the message I was getting. I let you know if it shows up again.
0 -
RandyM said:
Yes i did - i enable logging started the app - then quit the app and started again. Each time i start the app it says it quit un expected.
Note: i dont see the app crash. The system just says it did everytime I start the app.
When present with the dialog, are you clicking submit or cancel?
Mac Developer
Faithlife0 -
submit
0 -
I probably submitted 10 to 12 times over last 2 days... I had new resources etc. come down etc. and needed to restart app.... each time I just submit.
0 -
RandyM said:
I probably submitted 10 to 12 times over last 2 days... I had new resources etc. come down etc. and needed to restart app.... each time I just submit.
There was an issue with the crash reporting server that was causing the submission to silently fail. Since it failed to send the report, it would ask you to send it again the next time the application was started. The issue with the server has been fixed and you should no longer be seeing the crash report dialog after you click submit or cancel unless the application actually crashed the last time it was run.
I have created a case to see if we can't update the crash reporting framework we use so it does not repeatedly ask you to submit the same crash report if the submission fails.
Sorry for any inconvenience this caused,
Martin
Mac Developer
Faithlife0 -
Martin Potter said:
There was an issue with the crash reporting server that was causing the submission to silently fail. Since it failed to send the report, it would ask you to send it again the next time the application was started. The issue with the server has been fixed and you should no longer be seeing the crash report dialog after you click submit or cancel unless the application actually crashed the last time it was run.
I have created a case to see if we can't update the crash reporting framework we use so it does not repeatedly ask you to submit the same crash report if the submission fails.
Sorry for any inconvenience this caused,
Martin
Thanks Martin - that seems to have fixed it for me.
Running Logos 6 Platinum and Logos Now on Surface Pro 4, 8 GB RAM, 256GB SSD, i5
0 -
Thanks!
0 -
I'm now having this issue with each cycle of use. Each time I open Logos I get a crash report and each time I close Logos I get a crash report.
Just letting you guys know.
Thanks.0
