Beta 2.6.1 Crashes When Opening Resources

Hello,

After updating to Bible/Faithlife beta 2.6.1, the app crashes and closes when opening a Bible resource.

Open the app
Wait until the main screen opens
Either 1) tap the Read button on the action bar or b) tap any Bible resource from your history in the Go tab
The resource opens
After a few seconds a error message displays that says "Unfortunately, Bible/Faithlife has stopped"

However, by clearing app data, you are able to successfully open a resource after re-entering your authentication information.

I updated from the most recent beta build (sorry, I forgot the version number)

Device: Nexus 10 (Android 4.3)

I love the fact that it automatically downloaded the resources that I had previously downloaded after clearing app data. Nice touch.

Thanks,

Dan

Find more posts tagged with

Comments

Erwin Stull, Sr.

Same thing occurs on Samsung Galaxy Note2 and Galaxy Tab2 7.0 (both android 4.x), however, the vyrso app opens correctly.

Drew Hannay

https://community.logos.com/discussion/comment/517266#Comment_517266

We are looking into this crash and have a theory about what's happening. One of us will post back here when we have more information. As Dan mentioned, clearing your data (or uninstalling and reinstalling) should resolve this issue. (I realize this is a pain, but until we finish investigating, we can't say for sure if there's another way to fix it).

Erwin Stull, Sr.

https://community.logos.com/discussion/comment/517319#Comment_517319

Thanks Dan.

Thanks Drew.

Dan's workaround worked. Also, on my devices, it was not necessary to uninstall the app. Clearing the data worked fine. The drawback is that each of the resources will download again.

Drew Hannay

https://community.logos.com/discussion/comment/517320#Comment_517320

Okay, we've now confirmed our earlier suspicions...

The 2.5.1 and 2.5.2 beta releases had a bug which caused part of the data required for reading plans to not be stored on the device. This bug was fixed in the 2.5.3 release and only data on the local Android device was affected (no sync data was corrupted). Unfortunately, the Daily Reading improvements in the 2.6.1 beta will not work without the missing data that was left out by the 2.5.1 and 2.5.2 beta releases and causes the app to crash when attempting to load the data that's not there.

This should only affect users who installed one or both of the affected betas. The only way to resolve the crash is to either uninstall/reinstall the app or to "Clear data" for the app (both methods are essentially doing the same thing). This will force the app to pull down your sync data from the Logos servers and store it correctly.

We apologize for the inconvenience of having to reinstall (short of corrupting sync data, this is what we most try to avoid) but this is one of the risks of using beta software. Thanks for your understanding, patience, and continued testing efforts. Without our beta testers, bugs like this might affect many, many more users.

Robert B Harte

I started with the crash problem. After uninstalling the app on my Kindle Fire HD 8.9 and re installing as well as removing the earlier version from the cloud. I am able to get the app to launch, but I get a message "Unable to write to the SD card.and the app hangs up.

Gabe Martin

https://community.logos.com/discussion/comment/517887#Comment_517887

Robert,

Do you have your KF HD plugged into a computer when attempting to start the app? The apps require write access to the external storage location and this is inaccessible if your device is sharing files via usb. Just an idea.

Gabe

Quick Links

Recent Posts
Activity
Unanswered