Subscribe to Updates

Click here to subscribe to new posts by email. We use Google FeedBurner to send these notifications.

Archive for the ‘Product Updates’ Category

Why Have All My Books Been Updated?

Posted on: February 1st, 2012 by Craig Rairdin 2 Comments
If you’re using PocketBible on your iPhone or iPad, you may have noticed a message on the “Add/Remove Books” screen saying that many of your books have been updated. You’ll also see a similar message if you use PocketBible for Windows or one of the older mobile platforms and visit the “Downloads” page in your account at our website.

I mentioned in a recent Android update that we were going to have to rebuild all our books to support some new search features in the Android version of PocketBible. That turned out to be a 6-8 week rather than a 1-2 week exercise. Part of the reason is that since we had to touch every book that we publish, we used that opportunity to fix all the reported errors that we had on file for each book.

Many of these errors are all but invisible to the user. As a result we tend to let them accumulate for a while rather than jumping on every typo and minor formatting error as soon as we hear about it. The problem is that those things add up after a while and frankly our list had gotten overwhelming. We had one BookBuilder customer who volunteered to help a while back. He did a few books but then gave up. So this seemed like a great opportunity to just clean that list out since we had to look at every single book anyway.

In order to minimize the load on the server from everyone being told all their books had been updated, we created a way we could update the files on the server without the server thinking they had been updated. So the only time we allowed the server to know a particular book had been updated was if it was on the list of books in which noticeable changes had been made. If all we did was change “Laridian Electronic Publishing” to “Laridian, Inc.” (because one is our name and one is not) in the book’s meta data, we didn’t bother to have the server tell you about the change. But if we fixed a number of links or typographical errors — something you would notice — we had the server tell you about it.

We were also a little concerned about the load on the server if everyone went out and started re-downloading all their books. So we didn’t make a big deal about it, and we uploaded the books a few at a time over the last couple of months.

So if PocketBible or our website is telling you that a book has been updated, it means we fixed something that you might notice if you were paying close attention. In reality all the books were updated, but none of our programs currently make use of the new features that necessitated the update. So it’s only necessary to update the ones that say they need to be updated, and then you really only need to update them if you’re picky about every little typo.

PocketBible 2.0.3 Now Available on the App Store

Posted on: November 22nd, 2011 by Craig Rairdin 12 Comments

We just heard from Apple saying that 2.0.3 has been approved. You should already be seeing the update in iTunes on your device. We recommend everyone grab this update, as it fixes a few little problems. It also adds a couple of small enhancements that should make the program more enjoyable to use.

If you’re still running 1.4.7 or an earlier version you need to follow the instructions here to get this new version. Version 2.0.3 is not an automatic update to 1.4.7 or any 1.x.x version of PocketBible.


Double-tap on any image to blow it up in a window where it can be zoomed and scrolled. This is handy for maps and some of the detailed charts that appear in some study Bibles and reference books. It works best to go into Settings and tell it to fit images to the screen, then just double-tap them when you want to view them in detail.

If an image has links in it, those links are “hot” in the zoom view. Most images do not have links, but the maps in our Laridian Maps product do.

Books and voices are now marked as “non-purgeable” as they are downloaded. We got some reports that iOS would delete your books if it needed space for another app. This can be disturbing when you discover that books you spent a long time downloading are suddenly gone. By marking these as non-purgeable, Apple promises us they won’t delete them.

Note that while we retroactively mark your existing books as non-purgeable, and that we mark books and voices as non-purgeable as they are downloaded, we do not mark existing voices as non-purgeable due to the complexity of the file structure for voices. If you operate on the edge of available memory and want to make sure your voice files get marked as non-purgeable, you should delete them with Add/Remove Books, then download them again.

If there’s only one book open in a tab, we use that book’s abbreviation as the title for the tab rather than using the book’s category (“Bibles”, “Commentaries”, etc.) as the tab title.


On iOS versions prior to 3.2, there were controls to allow you to turn on the tabbed interface even if you didn’t own the Advanced Feature Set. Unfortunately this didn’t really give you the full features of the tabbed interface because the rest of the program would get confused by the fact that you had tabs turned on but did not own the Advanced Feature Set. This version fixes that by hiding those controls.

Printing, emailing, or texting the selected text could crash or do nothing. This has been fixed.

We believe we’ve fixed a problem in which the text window was offset right and up so you could see the gray background behind the text window. This only happened to some users and only under certain circumstances. We could only duplicate it on one of our iPhones. It wasn’t related to which version of iOS you were running or which type of device you had (though I think we only saw it on iPhones and iPod touch devices, not iPads). What it was related to was the version of the development tools we used.

Turns out Apple swapped out a portion of the compiler that converts our Objective-C programming code into the machine code that runs on the phone. The new compiler apparently generates flawed code. (Compare to what happens when an inexperienced translator flubs up the translation of a speech at the United Nations. The original speech is fine but the translation doesn’t say what the original speaker said. That’s what happened to our code. Our code was correct by Apple’s translation of it made the device do something different.) We fixed it by turning off all the special optimizations that the compiler can do for us. Hopefully another programmer will be able to demonstrate this bug in some simple way so Apple can fix it. We were never able to do it reliably, so we couldn’t report it.

As I said, everyone should install this update. You don’t need to re-download your books or voices, nor do you need to sync your personal data after you update. This is just a normal program update that won’t affect anything you’ve downloaded nor any of your notes, highlights, or bookmarks.

PocketBible 2.0.2 Available on the App Store

Posted on: October 21st, 2011 by Craig Rairdin 14 Comments

We’ve just been notified that our latest update to PocketBible (version 2.0.2) has been approved by Apple. It should become available in the App Store over the next 24 hours.

This update mostly affects people at either end of the range of supported iOS versions. For those of you still running some version of iOS less than 3.2 (primarily those of you with first-generation iPod touch devices running 3.1.3) you’ll finally get to see what PocketBible 2 looks like. Both the initial release and the 2.0.1 update had problems that prevented them from running on those devices. We had been relying on our development tools to tell us if we were using features of iOS that were not present on those older devices. Unfortunately, it turns out they are very silent on that issue. We’ve learned our lesson and have “downgraded” an old iPhone to 3.0 for testing. (Previously we were limited to running 3.2 in the iPhone emulator.) As a result we’ve been able to identify the issues that were preventing PocketBible from running on 3.0 and 3.1 devices.

On the other end of the iOS version spectrum we ran into an interesting bug in iOS 5. When we put verses on the pasteboard (that’s “clipboard” everywhere else but in Apple Land), we always store both a plain-text version and an HTML version. This allows applications that understand HTML to paste nicely formatted text, including superscripted verse numbers, words of Christ in red, and bold headings. Simpler applications expecting only plain text have the option of requesting just the plain text from the pasteboard.

When an application pastes data from the pasteboard, it specifies what format it wants. Unfortunately, in iOS 5, when an application asks for the traditional “utf8-plain-text” that has worked in all iOS versions since the beginning of time (OK, since iOS 2), the operating system will not give it the “utf8-plain-text” version of the pasteboard text, but instead will substitute something else — in our case, the HTML text that is also there. Since the pasting application neither expects nor understand HTML, it treats it as plain text and pastes it, tags and all, into your document.

To get around this, we have to add a third form of the text to the pasteboard, which is identified simply as “text”. This version is identical to the more correct “utf8-plain-text” that has worked on previous iOS versions. Doing this tricks iOS 5 into supplying plain text to apps that request it, so that pasted verses no longer include HTML tags.

On the subject of iOS 5, it introduced some new fonts and some new ways of identifying old fonts. Since iOS makes it very difficult to determine if a font provides the bold, italic, and bold/italic versions that PocketBible requires, we use a somewhat fragile technique to try to make that determination by looking at the names of the fonts. This didn’t work exactly right in iOS 5. The result was that Helvetica Neue was displayed as condensed and bold, and both Optima and Hoefler Text were missing from the list of available fonts. This has been fixed and the code reinforced so that hopefully it will do a better job identifying fonts in the future.

Some of you have had the unfortunate experience of selecting two or three verse and when you ask PocketBible to highlight the selected verses, it highlights the rest of your Bible. This happens when the end of your selection is right on the little gap between paragraphs. This is fixed in version 2.0.2 so that your entire Bible isn’t highlighted when you only want to highlight a couple verses.

Finally, probably because of the load that PocketBible 2 has put on our servers, many of you ended up with corrupted book files. Since PocketBible can’t read the file (the were corrupted during download) it can only identify the book by its 8-character alphanumeric file name. So you would see a message that “0065001d.lbk” was damaged, but there was no way to know what book that was so that you could re-download it. This message came up every time you ran PocketBible. The new version deletes damaged books automatically so that you won’t be nagged by warning messages.

For all the complaining we do about the App Store approval process, this update was approved in about 24 hours. Hard to complain about that!

PocketBible 2.0.1 Approved by Apple

Posted on: October 12th, 2011 by Craig Rairdin 19 Comments

We’ve just been notified that PocketBible for iOS version 2.0.1 has been approved. This is essentially an update that tries to squash the inevitable little bugs that show up in any x.0.0 version.

Some of you were completely unable to run PocketBible at all. Turns out if you weren’t running a relatively recent version of the operating system, PocketBible would display its splash screen then immediately exit. This has been fixed. We were all somewhat surprised we hadn’t found that problem before releasing the program, since it was trivial to reproduce once we set our minds to it. We get used to our programming tools warning us when we try to do something that’s not available in older versions of the OS and don’t always test for compatibility as thoroughly as we could.

Some of you were surprised to hear Heather or Ryan or one of our other voices start reading the Bible to you when you hung up after a phone call. Turns out if you paused PocketBible’s synthesized voice instead of stopping it, then any interruption would restart the reading. That was an easy fix once I figured out what was going on. Sorry if it caught you at an inopportune time.

This brings up an interesting point: You probably didn’t realize that the “mute” switch on your iPad or iPhone is only a “suggestion” to the device. You might think you’re turning off the sound, but you’re not. Apple treats the iPod app and other apps that play “foreground” sound (such as PocketBible) as immune from the effects of the mute switch. They believe you only intend to mute background sounds from games, key clicks, and that kind of thing when you flip the mute switch. Hmmm.

A couple of you reported that you only had two panes/tabs on your iPhone after upgrading to the Advanced Feature Set, instead of the advertised five panes/tabs. It could be fixed by exiting the program and re-launching. We were able to find the problem and fix it so you won’t have to do that in the future.

While printing out one of my own sermon notes I discovered the Autostudy CSS settings for ordered and unordered lists were overriding my list types. So my nice outline with roman numerals and upper/lower case letters was displayed with all arabic numerals. I made a change to the default CSS so this won’t happen.

Some of you were able to crash the program while doing a “Paste to Email” or “Paste to Text” operation. When we looked at the code, it looked like it should always crash, yet it never crashed for us and it didn’t crash for many of you. So this is one of those cases where we’re not sure why it ever worked at all. Nevertheless, it’s fixed in 2.0.1.

Finally, we got a nice note from Apple saying they were concerned about the effect our Bibles and books would have on the amount of data backed up to their new iCloud service. Data that can be re-downloaded from our server, they said, should not be stored in a directory that is automatically backed up. We see it the other way. We think you’d like to have your entire PocketBible library restored when restoring from a backup set, without having to separately log into our server (and any other server for any other program you might have with ebooks or other downloadable data). We read the developer documentation as “suggesting” that we don’t do that, so after considering the suggestion we decided to leave it the way it was.

However, Apple seemed really concerned about the few dollars this might cost them in additional hard drive space for iCloud, and given that they’ve gone through some tough times lately we decided to help them out. Version 2.0.1 automatically moves your books to a folder that does not get backed up to iCloud. So if you ever have to restore a backup, you’ll have to log into your account on our server and re-download your books. Just don’t everyone do it at the same time. :-)

PrayerPartner 1.2.1 Update Available

Posted on: April 25th, 2011 by Craig Rairdin 20 Comments

An update of PrayerPartner is now available in the Apple App Store. This update provides two new features.

See prayer requests in random order. PrayerPartner typically shows your prayer request in calendar order, either oldest to newest or newest to oldest, depending upon your preferences. As you consistently and repeatedly work through the various requests in the same order, you’ll find that you’ll recall the requests more and more, even during times when you aren’t using PrayerPartner. However, this same consistent presentation may result in an unintended staleness, as the requests never seem to change. If you find this happening to you, you can now choose to review your requests in random order. The requests will be randomized daily, so the order will be consistent on any given day.

Use iTunes Document Sharing to backup or move your requests to another iOS device. One consistent misunderstanding revealed in customer comments in the App Store is that PrayerPartner doesn’t backup its requests. In fact, iTunes performs backups every time that you synchronize, without PrayerPartner needing to do anything special. However, for those that like more control, or that want to directly move their PrayerPartner database to another device, PrayerPartner now supports iTunes File Sharing. This allows you to use iTunes to copy the PrayerPartner database from the iOS device to your host computer, and then copy it back to the same or another device. Note that this is a direct copy (not a merge), so the copied file will replace any existing data that is present. You should also be sure to exit PrayerPartner before copying data. For those that like to get under the hood, this new feature will allow some additional flexibility.

I hope that PrayerPartner users will find these new features helpful!

PocketBible 1.4.3 Available on App Store

Posted on: July 25th, 2010 by Craig Rairdin 22 Comments

The first of four new PocketBible products is available on the App Store. “PocketBible FREE” was approved earlier this evening.

We’re still waiting for approval on the Life Application Study Bible Collection, the NIV Study Bible Collection, and the NIV Reference Collection. These are primarily targeted at new users of PocketBible, but depending on the state of your PocketBible Library, you might find them to be valuable as an existing customer.

The new version features a built-in link to the PocketBible Bookstore. The approval snuck up on me this evening and I’m not quite done with all the tweaks to the product catalog. If you find a problem with any of the product pages, send me an email at Please don’t post them here.

Note that when you purchase a book from the built-in bookstore, we’ll eventually be able to tell PocketBible to automatically download it when you go to Add/Remove Books. That feature requires some more work on the server, which I hoped to get done this weekend but it’s looking less and less likely. Soon.

This version should also fix any lingering task-switching problems for iPhone 4 owners.

Now on the App Store: PocketBible 1.4.2

Posted on: July 12th, 2010 by Craig Rairdin 31 Comments

We’ve updated PocketBible to fix an annoying little problem on iPhone 4 in which what we call the “launch options” screen is displayed when you re-start PocketBible after the OS has dumped it from memory while it was idle. While we were in there, we added a couple little features:

iPhone and iPad Features

  • Added an option to enable/disable the use of colored buttons in the Bk/Ch/Vs verse selection forms to indicate sections of the Bible. Some people really hated what one of you called the “funky button colors” so we gave you the option to use a very un-funky gray for all the buttons.
  • Added an option to set margins and line leading for single- and multiple-pane screen configurations. Some people wanted to see more text on the screen in the single-pane mode. This lets you do that. While we were at it we gave you the option of setting margins and leading in the multiple-pane view, too.
  • Fixed a bug in which the temporary highlighting of the linked-to verse could disappear after synchronization with our server, removing or updating books, or coming out of the suspended state (iOS 4).

iPhone-only Features

  • Added “Split Screen” to Context menu. It’s a little more convenient there than going to Menu, Settings, Open Panes, and choosing “2”.
  • Fixed a bug that caused the launch options form to sometimes be displayed when coming out of the “suspended” state.

The next update won’t have any new features in it per se, but gives us the ability to sell our “collections” on the App Store and sets us up for in-app purchasing of books.

PocketBible and PrayerPartner Updates Submitted to App Store

Posted on: June 25th, 2010 by Craig Rairdin 19 Comments

Today we submitted PocketBible 1.4.1 and PrayerPartner 1.1.0 to the App Store.

PrayerPartner has been updated for iOS 4. This is primarily related to making PrayerPartner aware of and compatible with multitasking. However, we are also taking advantage of a new feature of iOS 4 – a programmatic interface to the text messaging composition form. PrayerPartner has previously helped you send emails regarding requests on your prayer list. Now it can also help you send text messages.

We also took this opportunity to add some email and text messaging capability to PocketBible. While I ran into some problems that prevented me from including these features in our 1.4.0 update, those issues have been resolved. PocketBible now allows you to send Bible verses via email or text messaging to people in your contact list.

Note that the text messaging features are only available with iOS 4, and your device must be capable of sending text messages.

As always, we expect the approval process to take 2 to 10 days. When the updates are approved, iTunes will notify you that the updates are available.

App Store Updates: PocketBible 1.4.0 and RomansRoad 1.0.3

Posted on: June 24th, 2010 by Craig Rairdin 21 Comments

This posting has been edited to reflect the fact that PocketBible 1.4.0 and RomansRoad 1.0.3 are now available on the App Store. Comments prior to the afternoon of 24 June were posted before the apps became available for download.

Both PocketBible and RomansRoad have been updated to account for new features in what Apple calls iOS 4 — version 4.0 of the iPhone OS.

What this boils down to is that the app saves its state when it is notified that the user wants to switch to another app, then restores its state when the OS notifies it that the user has switched back to it. These hoops would be completely unnecessary if Apple implemented “multitasking” the same way Windows, Windows Mobile, and even the Mac OS implements it. That is, your app doesn’t have to do anything special to run at the same time as other apps on those platforms. Leave it to Apple to reinvent the wheel — and the axle, differential, drive shaft, and engine. :-)

The new version of PocketBible also implements several changes related to notes, highlights, bookmarks, and synchronization with the server:

  • When saving notes we used to convert “special characters” like emdash, left- and right-double-quotes, bullets, etc. into HTML character entities. This is unnecessary and can be confusing the next time you open the note.
  • When synchronizing notes with the server, we’re doing a more consistent job of handling those special characters.
  • Previous versions made sure all the Toolbox panes were kept up-to-date even when they were not the active pane. As a result you could spend a lot of time waiting for a list that you never look at to be updated. The new version only updates panes when they are active or become active. This should speed up launching and updating the screen after synchronizing with the server.
  • We sped up synchronization of large data sets by making some changes on the server but also by changing the algorithm that iterates over the notes on your device. This also sped up searching of notes.
  • We gave you the ability to change the length of time the program will wait for a response from the server when synchronizing your data. This mostly affects users with a large number of notes, highlights and/or bookmarks (say, greater than 1000 of any of these).
  • We optimized the case where you’re not really searching your notes but just asking for a list of all the notes in a particular Bible. This affects how quickly the Find Notes pane in the Toolbox can be updated.
  • A previous version of PocketBible broke the rotation lock function on the iPhone. It is fixed in this version.

We still have a couple features we’re working on that take advantage of some iOS 4 features. If we can get those to work, they’ll be in 1.4.1.

Final Update on Synchronization Progress

Posted on: June 9th, 2010 by Craig Rairdin 22 Comments

Good JobToday we uploaded version 1.012 of PocketBible for Windows, and version 1.002 of the Server Synchronization Provider (formerly known as the iPhone Sync Provider). These updates address three issues:

  1. Notes containing certain special characters could become corrupted in the synchronization process as those special characters were passed from platform to platform, each of which may have treated them differently.
  2. Because of differences in the way the PC and our server implemented the synchronization algorithm, “old” data from the PC could be deleted when syncing with existing data from an iPhone.
  3. Since we were making changes, we also changed the way the PC keeps track of the date/time of the last sync. The new method eliminates rare problems caused by differences in the system time between the server and your PC.

To get the latest version of PocketBible for Windows, simply log into your download account, download it, and install it.

To get the latest Server Sync Provider to replace your old iPhone Sync Provider, go to the PocketBible for Windows site ( and select “Synchronization Providers” from the Products menu at the top of the page. Follow the instructions near the bottom of the page to download and install the Sync Provider.

The previous version of PocketBible should refuse to work with the new sync provider, and the new sync provider will refuse to work with the old version of PocketBible. So if you don’t get them installed correctly the program will tell you.

An important new feature added to PocketBible for Windows is the ability to reset your sync history. This forces PocketBible to treat the next sync as if it is the first. If you ever have to restore your PocketBible for Windows user data database, you’ll want to reset the sync history or you risk confusing the sync algorithm. When it sees that you have old data in your database that is no longer on the server, it will delete the data you just restored from your backup (thinking that you deleted it from the server). If you reset your sync history, it may find duplicates and ask you about them, but it won’t delete anything.

iPhone/iPad Users: There will be an update to the iPhone/iPad version of PocketBible to make some adjustments to the way certain special characters are handled. We currently are planning to roll this into our “iPhone 4” update, which will be uploaded to Apple just as soon as we can.

Thanks for your patience while we worked on these updates.

©2015 Laridian