I’d be open to the Logseq sync in lieu of multi cloud sync. But as of now Logseq sync a) doesn’t happen in the background b) can be slow on loading, c) can lead to merge conflicts or worse yet, silent failures that go unnoticed. Hence using one of the cloud providers sounds like a promising alternative.
1 Like
Why are remote providers disabled?
Although, Shellfish is enabled. Don’t these all use the same API on iOS?
1 Like
If you have a Synology drive that supports docker - I believe there is now an official docker image Package logseq-webapp · GitHub
I was about to start using the app as my main knowledge gathering tool. Created a Proton Drive folder to use whether I stay with Apple or not, and then went to access it via the iOS app, no joy. Searched, found this thread. Realized that this is not the app for me. Deleted. A privacy-centric app that doesn’t really support privacy.
1 Like
It would be great, but should be universal enough that it could work with a variety of services, such as e.g. pCloud, Nextcloud…
1 Like
+1 for Proton Drive. I like how easy the iCloud drive setup is on iOS and iPadOS, and it seems like it could be just as easy with Proton Drive.
For people hating on Logseq for not supporting third-party sync on iOS: you should be angry at Apple, not the Logseq developers.
If we could offer it, we would. But the way iOS’s sandboxing works, apps only have write access to their own directory (either on iCloud, or on the local device). Any other directory can only be read.
So even if we wanted to, we couldn’t support third-party sync for Logseq on iOS, because Logseq doesn’t have write rights to the directory of other apps due to Apple’s security policies.
Who’s hating on anybody? I’m just asking for them to support Proton Drive using the existing file access facilities built into iOS.
Defensiveness is probably not the play right now, it’s just a feature request y’all.
It was not specifically aimed at you @manchicken but in general after reading the messages in this thread (some of which are very indignant).
Also, no defensiveness here: I’m just explaining why things are the way they are, especially as this is one of the most popular feature requests. Plus, it’s one of the most common questions I get via the support inbox. That’s why I’m chiming in here.
I know for a fact that the devs would have added this feature if they could. Unfortunately, they can’t as I explained in my previous reply. Because of Apple’s limitations in iOS there is no way for the Logseq devs to add support for anything other than iCloud or Logseq’s own syncing service (as Logseq has access to its own folders only).
So while you can access files in third-party cloud services via iOS’s Files app, that doesn’t mean other apps can access those same third-party cloud services/drives. Apple has closed that off as they believe in sandboxing, preventing apps to write to other app’s folders.
If you (or anyone) knows of some way to still enable full write access to third-party folders in iOS, I’m sure that the devs are all ears.
Just going to chime in here with a reference to DevonThink and their sync system.
Their forum is also full of people dealing with sync issues and similar problems.
What I will say though is that their Dropbox sync works well over MacOS and iOS. I use it across 7 databases all day, every day.
The DT devs and support people frequently push their Bonjour sync that works differently from Dropbox and iCloud sync. I am not informed enough to explain that difference other than to say that Bonjour sync is only for devices on local networks. I’ve gone months without resorting to Dropbox sync when my phone, iPad and Laptop were always on the same network at least once every day. Now that I have two desktops and a laptop in different offices I rely on Dropbox sync.
Lots of DT users have problems with the iCloud sync and the general response to those problems is that most of those issues lie with Apple and the inscrutable way their cloud service works. But there are also lots of people who use the iCloud sync for years and never have a problem.
I am sure software coders <sarcasm>love</sarcasm> to hear “these other people do it, why can’t you” but in this instance there seems to be overlapping styles of software and database styles, at least based on where the DB version of LogSeq is headed. DevonThink is Mac only though so maybe that makes this whole thing moot.
I love both Devonthink and Logseq and they’re both crucial parts of my day to day workflow.
Keep up the good work.
1 Like
I think what you’re looking for would be to do with UIDocumentPickerViewController, but I’m not certain.
Also, Apple includes two code-level support requests per year as part of the Apple Developer program. Have y’all reached out to them for code-level support here? It might not be something super easy to do on the JS side of the app, but it should be possible.
I’m not an iOS developer anymore, but I’ve done iOS before. I still have an app in the Mac app store, and last year I had to reach out to Apple’s code-level support folks for an Xcode filesystem related issue and they were super helpful. It took them a few round-trips to understand what I was having a hard time with, but we got there and they were super helpful.
I’m not a dev myself, but from the Apple docs I got the idea this is just to read files, not to write files.
We currently have no iOS dev contributing to the project, so this will be difficult. I’m lobbying internally to find a way to attract an iOS contributor, but will limited funds it will be difficult I’m afraid.