PSPDFKit automatically saves annotations at certain trigger events. This mechanism works well, but there’s still the possibility of losing data if the device restarts or runs out of battery, or if your application crashes before a save completes.
With document checkpointing, PSPDFKit offers a checkpointing mode that works in the background, providing an effective crash recovery mechanism to restore unsaved changes. This is an advanced feature that’s disabled by default, as it requires some configuration to work effectively.
PSPDFKit Instant stores annotations in a database and synchronizes with your PSPDFKit Server as soon as a connection is available, which greatly reduces the chances of data loss if the app terminates suddenly. No checkpointing or other custom setup is needed. Read more in our Instant Offline Support guide.
Understanding Document Checkpoints
A checkpoint contains all the unsaved data in a document. For the sake of this explanation, let’s call this the “dirty” data. This data is temporary and persisted into the document when
Document.save(options:) is called. With document checkpoints, this dirty data can be continually saved to a separate checkpoint file, and in the event of a crash, it can be restored to the document.
The following strategies are available:
.manual— the checkpoint has to be saved manually by calling
DocumentCheckpointer.saveCheckpoint(completionHandler:). This is the default.
.timed— the checkpoint will be saved at a preset interval, as long as the document exists and there are unsaved changes.
.immediate— the checkpointer reacts to changes made to the document, saving a checkpoint every time a change is made.
For most use cases,
.immediate is a good option and does not affect performance by any significant amount.
Loading a Saved Checkpoint
To load a previously saved checkpoint, you must use the appropriate
Document initializer —
YES to the
loadCheckpointIfAvailable parameter loads the checkpoint, if it’s available. It’s important to note that while the document will contain any previously unsaved objects saved in the checkpoint, the loaded changes are not saved to the document. To do this, you must still call
Document.save(options:). This will cause the data from the checkpoint file to be written into the document, after which point the checkpoint will be deleted from disk by the
Supported Document Types
Documents that are backed by more than one provider are not currently supported by document checkpoints. Documents that are not backed by a file (
Data/custom data provider) work well checkpointing, as long as certain care is taken with regard to their UID. When enabling checkpointing on a document that uses a custom UID, one must be sure that the UID is unique to that document, since the
DocumentCheckpointer uses the UID as a part of the checkpoint’s file name. Opening multiple instances of a document with the same UID and making changes to them while they have checkpointing enabled is not supported and will result in undefined behavior.
The checkpoints are stored in a subfolder in the device’s Library (more info) folder. You do not have to manage this manually since each
DocumentCheckpointer will always delete the document’s previous checkpoint before saving the new one. Additionally, the directory in which the checkpoints are stored is cleaned up by removing any checkpoints that are older than a week. The checkpoints are not shared between the main app executable and any of its app extensions, since the
Library directory is unique to each of them. Therefore, if an extension crashes while a document has unsaved changes, those changes will not be recoverable from the app or another extension.
There are two things to consider with document checkpointing in terms of performance:
- Saving — Depending on the strategy, the
DocumentCheckpointersaves checkpoints to the location specified above on a low priority background queue. This should not affect your application’s performance in any meaningful way.
- Loading — When loading the checkpoints as specified above, the loading of a document may take a little longer than usual since that is when the document is parsed, but the initializers of
Documentare not affected. Since
Documentonly parses the document when it is actually required, you might see a small slowdown when accessing properties that require parsing.