Logos 5.1 Crashing
You guys are killing me with these updates. I thought that when you updated a piece of software, you made it better? Why is it that every time you guys release an update, we go through this?
Comments
Hi Erik,
Sorry you're having this problem.
This crash is caused by a reference range synced from your Android phone. (See also this post by a Windows user experiencing the same problem: http://community.logos.com/forums/t/72267.aspx.)
Your app is probably crashing as soon as the Bible Search panel (which is in your startup layout) is opened. To stop this, please hold down the CMD key as you start the application. When the Sign In dialog appears, check the "Use blank layout" checkbox then click Sign In. You will now be able to use Logos 5.1 except for Bible Search.
We will be fixing this in 5.1 SR-1. The workaround for now is to delete the custom reference ranges you have created on the Android phone and let them sync back to your Mac.
I will try your solution.
Only one problem. I don't have an Android phone. I haven't had once since last October when I went to the iPhone 5. And when I DID have an Android phone, the app did not allow custom reference ranges, so I never set any.
And not having Bible Search kind of defeats the entire purpose of having Logos BIBLE Software, don't you think?
Only one problem. I don't have an Android phone. I haven't had once since last October when I went to the iPhone 5. And when I DID have an Android phone, the app did not allow custom reference ranges, so I never set any.
Sorry for the incorrect assumption. It may also be possible to cause this crash from editing custom ranges on the iPhone.
If you use the Logos app on your phone, you can go to the Search tab, then tap Bible, then tap the rightmost button under the "Find" box (it may or may not be labelled "All Passages"). In that screen, you can edit and delete custom ranges, which should sync back to your Mac and fix the problem.
And not having Bible Search kind of defeats the entire purpose of having Logos BIBLE Software, don't you think?
We will be fixing this in the next update.
Sorry, Bradley but after years of being told things are going to be fixed in the next update, it starts to get a little old. Do you have any idea how frustrating it is for a pastor to have his Bible software unresponsive on Friday afternoon and then be told I can't use the Bible Search on the software?
I am a diehard Logos user, and I have been for years; but you guys have got to stop pushing out updates that are not ready for public use.
I put Logos DLS and Logos Bible Software 3 through the wringer for years and I never had a problem with them. I was one of the first to upgrade to Logos 4 on my Mac, only to discover that it was an ALPHA; and I spent the next 18 months just trying to keep up with the daily updates because someone should have stopped the decision makers and said, "It is a TERRIBLE idea to release an alpha to our user base."
And now we have 5; and it seems like every time it starts working properly, there's another bug. I think I speak for everyone I know who uses Logos when I say this: hold your updates until you have thoroughly tested them.
At the very least, give us a rollback option so that when something like this happens, we can restore to the previous stable iteration.
Understand your frustration. I guess I haven't had the issues you have had.
The log file reveals an error I haven't encountered. It is different from the one Bradley Grainger referred to in the other thread you posted to. Since you are on a Mac it might be one of the Mac guys will know how to help.
Pastor, North Park Baptist Church
Bridgeport, CT USA