iOS Reader Suite 9.14.0 (23) Stable Release Notes
The Mobile team is pleased to announce the 9.14.0 Stable release of the Logos, Faithlife Study Bible, Biblia, Faithlife Ebooks and Verbum apps. The apps should soon be available on the App Store.
If you discover any issues please open the Help menu and tap Report a Problem, and include the following information in your email:
Description – How were you using the app when the problem occurred?
Reproduction Steps - Please clearly explain how to reproduce the issue.
App Info – Which app you are using (Logos Bible, Verbum, Faithlife Study Bible, Faithlife Ebooks or Biblia).
Device Info – (iPad Pro 9.7, iPhone X, iPad Pro 11", etc.)
iOS Version – (14.1, 15.4.1, etc.)
For more information on reporting bugs please see https://community.logos.com/forums/t/173719.aspx.
Fixed
- Improved editing of sermon titles.
- Handle new Biblia URL formats when opening links.
- Guides now respect user-customized library metadata.
- Guides now use a more appealing font, consistent with the rest of the mobile app.
- Fixed an issue in Exegetical Guides rendering verse context.
- Other minor fixes.
Comments
-
My Phone is an iPhone 8, IOS is 14.3. After I updated Logos 9.14.0 yesterday, I could not open the app anymore, everytime I tried to open it, it would crush immediately, please help fix it or please provide a solution for this. I am not able to read my book on my iPhone now.
Thanks
0 -
Just for info:
https://wiki.logos.com/iOS_Release_Notes
which keeps track of which versions are supported. You appear to be supported.
The first test I'd make (before uninstalling/reinstalling), is download another of the Faithlife readers (eg Verbum) and see if they run 'clean' (before downloads, layouts, etc)?
0 -
My Phone is an iPhone 8, IOS is 14.3. After I updated Logos 9.14.0 yesterday, I could not open the app anymore, everytime I tried to open it, it would crush immediately, please help fix it or please provide a solution for this.
We apologize for the inconvenience. We've discovered an issue for users running iOS 14. We've submitted a fix, which is currently under review by Apple. We hope it will be available some time tomorrow. In the meantime, there is a work-around, which is to update your device to iOS 15.
0 -
Thanks You so much ^_^
0
