In order to ship a database with my iOS/PadOS app in the most space-efficient manner, I am adding a non-editable store to the app’s bundle and referencing it directly. I believe this is the approved method, and it seems to be working as expected.
I have made a small Mac app for performing the actual edits, since it involves a lot of text editing and formatting. It’s simply easier and less discomforting to use a keyboard for this, and it also lets me copy-paste more easily from other sources to cut down on my typing. I then grab the store files from their resting place and run the following code in Terminal to ensure that no data is missing due to Write-Ahead Logging. source.store is the filename of my database.
sqlite3 source.store
PRAGMA journal_mode = off;
VACUUM;
PRAGMA journal_mode = on;
The source.store file can then be neatly bundled into the iOS app. This all works very nicely and I’m happy with it. However, when I launch the app, I get the following warning messages in the log output:
CoreData: error: This store file was previously used on a build with Persistence-1523 but is now running on a build with Persistence-1522.
Is this something I need to worry about? I’d really rather not have esoteric warnings in my build logs, but I’m not sure how to get rid of the error. Is there something else I need to do when prepping the store file for use that will change the Persistence number to 1522?
