Codebook for iOS 3.6.0 Released - Password AutoFill and Free Trials

Our latest version of Codebook for iOS is fully compatible with iOS 12, and includes two pretty significant changes:

  • Password AutoFill support for iOS 12
  • Free Trials via In-App Purchase (don’t freak out, read on!)

Password AutoFill is a new feature in iOS 12 that allows you log into websites (and apps) with passwords stored either in your iOS device’s Keychain, or your favorite password manager, Codebook! Here is a quick demo of it in action:

The Password AutoFill feature requires iOS 12; if you cannot upgrade just yet, check out Find in Codebook.

Alright, here’s what’s going on with the In-App Purchases: we are not switching to a “freemium” model (what a loathsome portmanteau!) Instead, Codebook will be free to try before you buy, and everyone who’s already bought the app is grandfathered in.

Until now Codebook for iOS has been available to download for an up-front purchase of $9.99. Starting with version 3.6.0, we’ll be making the app free to download, and free to use for two weeks, after which an In-App Purchase of Codebook Pro is required to unlock the editing and sync capabilities. Codebook Pro is a one-time purchase of $9.99, additional purchases are not required to use it with more than one device as long as you are using the same Apple ID in the App Store.

If you purchased Codebook for iOS before version 3.6.0, you are exempt from our use of In-App Purchases, because you paid up-front for the app, sight unseen, cash on the barrel, without even being able to try it first! We remain deeply grateful for your support. You will not be prompted to make an In-App Purchase, but you can see your grandfathered license status on the Settings view.

Changes in this version:

  • Free to download as noted above
  • Adds new Codebook Pro In-App Purchase for new customers
  • Adds support for iOS 12, fixing various layout issues across device sizes
  • Adds new Password AutoFill support
  • Improves login view layout
  • Fixes margin and separator layout issues on the Database Info view
  • Fixes Search view animation bug when returning to search results from a selected result
  • Fixes failure to properly reschedule sync reminder notification after a successful sync
  • Fixes biometric authentication name referenced on Touch ID and Face ID errors when either becomes unavailable (no more “(null)”)
  • Fixes not removing section header in partitioned entries list when deleting last entry in last section of table


Visit this link on your iOS device to download Codebook from the iTunes App Store.


As always, please let us know if you’re having a problem with the software or have any feedback. If you like Codebook and you’re pleased with our progress, please consider giving us a rating or a review in the iTunes App Store, they help quite a bit!

This is very useful but I have some concerns. How does Safari know that I have a login for say Does it decrypt the database on every website load, or cache the emails/usernames in some way?

Hi @Felghana

Thanks for using Codebook and posting on the discussion forum.

Does it decrypt the database on every website load

No, the database is only decrypted once you select a credential and choose a credential to fill, then authenticate with the Codebook interface at which point Codebook will pass the password back through to AutoFill to be used for filling.

or cache the emails/usernames in some way?

Yes, this is closer to the correct idea overall. Codebook provides AutoFill with credential identities which involve email/username + serviceIdentifier combos – but not passwords (service identifiers are how AutoFill knows which email/usernames to associate with which websites/apps). This occurs once for all your data once AutoFill is initially setup (it will prompt you to configure it when you first enable it in settings) or the next time Codebook is unlocked after you enable it. After which, this “store” will be updated as you edit data within Codebook. Once you select one of these identities to fill, Codebook will present it’s interface to authenticate you, fetch the appropriate credential’s password, then pass it on through to AutoFill for filling into the appropriate field.

Most of the documentation Apple has available on the subject is somewhat technical, but there’s a pretty good overview of the high level points in this document: Apple Platform Security - Apple Support (starting on page 73). Specifically this excerpt:

Users can designate a conforming third-party application as a credential provider to AutoFill in Passwords & Accounts settings. This mechanism is built on extensions. The credential provider extension must provide a view for choosing credentials, and can optionally provide iOS metadata about saved credentials so they can be offered directly on the QuickType bar. The metadata includes the website of the credential and the associated user name, but not its password. iOS will communicate with the extension to get the password when the user chooses to fill it into an app or a website in Safari. Credential metadata is stored inside the credential provider’s sandbox, and is automatically removed when an app is uninstalled.

At this years WWDC (World Wide Developer Conference) they had a good presentation on how to implement AutoFill Credential providers in third party applications, like password managers (Codebook) which can provide credentials to other applications. Again, while this video is mainly technical, there are some pretty good visual diagrams about that’s going on when you select a credential to use for AutoFill. Here’s a link to the video: WWDC18 - Videos - Apple Developer There’s an overview of what’s happening when a credential is displayed and selected within the QuickType bar starting at about the 8:00 minute mark.

Let me know if this clarifies how AutoFill works, and if there’s anything else I can do to assist. Thanks!