Table of Contents
Naturally, I was quick to respond and got mine within hours. However, it took me much more time to sync my existing database using iCloud. Which is why I thought it would be helpful to me and others to compile what I know in a short blog post.
To start with Logseq on iOS will only read and index files out of an iCloud folder, named Logseq.
I suppose, this has to do with permissions. In a way, this is similar to how Obsidian works with iCloud. Once inside the Logseq folder, however, there is no limit on how many different databases you can store.
The easiest way to manage things is to simply drop your existing Logseq database inside this folder, and open it on the iOS side.
Note that if you have been using git to sync your notes until now, you should still be able to do so. The only thing to remember is that your
.git folder may not be equally readable by multiple git clients (e.g. your home, and your work laptops). It is therefore advisable to store versions in git from the same machine, with which you initialized or cloned the git repository.
Caveats with the iCloud synchronization #
I was happy to see Loqseq on my iPad, only to realize that it wouldn’t sync my existing notes. The thing is, iCloud folder contents wouldn’t download automatically until accessed for the first time. I suppose, this is something that Logseq would solve with a future update, but for the time being, there is a clever fix, involving an Apple shortcut by a Twitter user Aryan Sawhney:
This shortcut would simply recursively check the file size of every file in the shared Logseq folder, causing it to get downloaded locally. I suppose, this is an approach that could be implemented in a future Logseq update.
The same person shared a helpful tutorial on YouTube that’s worth checking out:
Have something to say? Join the discussion: