Generating list of change sets and updating work items
When reporting Realm issues, please be sure to include these auxiliary files along with your main You can refer to our migration sample app for an example of how to use a bundled Realm file.
In some scenarios you may wish to limit which classes can be stored in a specific Realm.
On i OS 8 and above, files inside apps are automatically encrypted using exception will be thrown.
In order to handle this, it is necessary to ensure that the file protection attributes applied to both the Realm file itself and its auxiliary files is downgraded to a less strict one that allows file access even when the device is locked, such as .
For example, suppose you have an application where users have to log in to your web backend, and you want to support quickly switching between accounts.
You could give each account its own Realm file that will be used as the default Realm by doing the following: The most common location to store writable Realm files is the “Documents” directory on i OS and the “Application Support” directory on mac OS.
This will ensure the attribute is properly applied to all of the relevant Realm files, regardless of their creation time. A synchronized Realm uses the Realm Object Server to transparently synchronize its contents with other devices.
For a detailed discussion about Realms, please read .If opening a Realm requires a time-consuming operation, such as applying migrations, compaction or downloading the remote contents of a synchronized Realm, you should use the In some cases, you might not want to open a Realm until it has all remote data available.