I have a folder I’m sharing between Linux, Mac and Windows. That all works fine. But when I try to share it from my Linux box to my Android (Pixel 5), after accepting the share there (in the web GUI) I get the error “folder path missing”. I’ve tried setting the local folder as the default (~/Logseq Notes) and putting it in Documents (~/Documents/Logseq Notes), with no difference. The Android web GUI says ~ is a shortcut for /storage/emulated/0 which should be correct on my device. I also tried using that full path, no difference.
Could it be a permissions issue? Where should I put the Android folder so it works? Note that I do have some other folders syncing OK, like /storage/emulated/0/Documents/Logseq-config. I can see that path in my Android’s Files app.
Logs from the Android device:
2023-11-02 08:57:00 Enabled debug data for "fs"
2023-11-02 08:57:49 Ignoring folder "Logseq Notes" (pqyse-kbhzm) from device 3C4BTR6-35E5VHE-UHDPAKL-CRDQMCZ-BR4YXGH-ALRKK27-TDXKH76-RXAYMAO since we are configured to
2023-11-02 08:57:49 Device QJJKGVT folder "Logseq Notes" (pqyse-kbhzm) has mismatching index ID for us (0x153A689E0491F869 != 0x0000000000000000)
2023-11-02 08:57:49 Device QJJKGVT folder "Logseq Notes" (pqyse-kbhzm) has a new index ID (0x37BC64955CCEF1F8)
2023-11-02 08:57:49 Unexpected folder "Logseq Notes" (pqyse-kbhzm) sent from device "QJJKGVT-BSFFIVV-MD2HNMM-3BQR5FL-I4L42OV-VTOYCZB-V722CDP-XRKKZAV"; ensure that the folder exists and that this device is selected under "Share With" in the folder configuration.
2023-11-02 08:57:52 api.go:1754 basic /storage/emulated DirNames . [] open /storage/emulated: no such file or directory
2023-11-02 08:57:52 api.go:1754 basic /storage/emulated/0 DirNames . [Android Music Podcasts Ringtones Alarms Notifications Pictures Movies Download DCIM Audiobooks Documents ... .$Trash$] <nil>
2023-11-02 08:57:52 api.go:1761 basic /storage/emulated/0 Stat Android {0x4001e1a180} <nil>
2023-11-02 08:57:52 api.go:1761 basic /storage/emulated/0 Stat Music {0x4001e1a240} <nil>
2023-11-02 08:57:52 api.go:1761 basic /storage/emulated/0 Stat Podcasts {0x4001e1a300} <nil>
2023-11-02 08:57:52 api.go:1761 basic /storage/emulated/0 Stat Ringtones {0x4001e1a3c0} <nil>
2023-11-02 08:57:52 api.go:1761 basic /storage/emulated/0 Stat Alarms {0x4001e1a480} <nil>
2023-11-02 08:57:52 api.go:1761 basic /storage/emulated/0 Stat Notifications {0x4001e1a540} <nil>
2023-11-02 08:57:52 api.go:1761 basic /storage/emulated/0 Stat Pictures {0x4001e1a600} <nil>
2023-11-02 08:57:52 api.go:1761 basic /storage/emulated/0 Stat Movies {0x4001e1a6c0} <nil>
2023-11-02 08:57:52 api.go:1761 basic /storage/emulated/0 Stat Download {0x4001e1a780} <nil>
...asic /storage/emulated/0 Stat SuperLapse {0x4001e1b2c0} <nil>
2023-11-02 08:57:52 api.go:1761 basic /storage/emulated/0 Stat .$Trash$ {0x4001e1b380} <nil>
2023-11-02 08:57:55 Connection to DASUXYK-... at 192.168.0.204:22000-192.168.0.200:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P30 closed: reading length: read tcp 192.168.0.204:22000->192.168.0.200:22000: read: software caused connection abort
2023-11-02 08:57:55 Connection to QJJKGVT-... at 192.168.0.204:47300-199.195.251.28:22067/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P50 closed: reading length: read tcp 192.168.0.204:47300->199.195.251.28:22067: read: software caused connection abort
2023-11-02 08:57:55 Connection to 3C4BTR6-... at 192.168.0.204:22000-192.168.0.124:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P30 closed: reading length: read tcp 192.168.0.204:22000->192.168.0.124:22000: read: software caused connection abort
2023-11-02 08:57:55 Adding folder "Logseq Notes" (pqyse-kbhzm)
2023-11-02 08:57:55 ignore.go:383 basic /storage/emulated/0/Logseq Notes Open .stignore <nil> open /storage/emulated/0/Logseq Notes/.stignore: no such file or directory
2023-11-02 08:57:55 model.go:401 basic /storage/emulated/0/Logseq Notes Hide .stfolder <nil>
2023-11-02 08:57:55 model.go:402 basic /storage/emulated/0/Logseq Notes Hide .stversions <nil>
2023-11-02 08:57:55 model.go:403 basic /storage/emulated/0/Logseq Notes Hide .stignore <nil>
2023-11-02 08:57:55 Ready to synchronize "Logseq Notes" (pqyse-kbhzm) (sendreceive)
2023-11-02 08:57:55 tempfile.go:51 basic /data/user/0/com.nutomic.syncthingandroid/files OpenFile .syncthing.tmp.392248251 194 -rw------- {0x40022ba040 .syncthing.tmp.392248251} <nil>
2023-11-02 08:57:55 atomic.go:94 basic /data/user/0/com.nutomic.syncthingandroid/files Lstat config.xml {0x40000dee40} <nil>
2023-11-02 08:57:55 atomic.go:99 basic /data/user/0/com.nutomic.syncthingandroid/files Rename .syncthing.tmp.392248251 config.xml <nil>
2023-11-02 08:57:55 atomic.go:113 basic /data/user/0/com.nutomic.syncthingandroid/files Chmod config.xml -rw------- <nil>
2023-11-02 08:57:55 atomic.go:125 basic /data/user/0/com.nutomic.syncthingandroid/files Open . {0x4002590238 .} <nil>
2023-11-02 08:57:55 folderconfiguration.go:121 basic /storage/emulated/0/Logseq Notes Stat . <nil> stat /storage/emulated/0/Logseq Notes: no such file or directory
2023-11-02 08:57:55 folderconfiguration.go:121 basic /storage/emulated/0/Logseq Notes Stat . <nil> stat /storage/emulated/0/Logseq Notes: no such file or directory
2023-11-02 08:57:55 Failed initial scan of sendreceive folder "Logseq Notes" (pqyse-kbhzm)
2023-11-02 08:57:55 Error on folder "Logseq Notes" (pqyse-kbhzm): folder path missing
Please try using the native app UI instead of the Web GUI. As you said, this is likely a permission issue, and the file explorer (which should open automatically when using the app UI) will tell you which folders you can use and which you can’t.
When I try to use the native app UI, it doesn’t pop up an Accept Share window though? I’ll try it again…
The exact wording will be different depending on your file explorer app, but it should look more or less somewhat like this.
Ah, I see – as of a recent version of the Android app (?) it pops up a share notification. I successfully used that to add the folder, and when I do, it apparently grants permissions in a way that the Web UI doesn’t. Seems like it’s syncing away merrily now, and the Folder Type is “Send & Receive”. Thanks!
Exactly, for some time now Android has required an extra step to get user to confirmation before the path can actually be used. We cannot trigger that from within the Web GUI (as long as just entering a path as text). Thus you basically have to use the wrapper for adding, unless it’s beneath a hierarchy that has previously been granted access to.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.