I’ve been attempting to set up syncthing such that I could have my Minecraft worlds sync between PC and Android. I gave root permissions to the last build of syncthing-android, and successfully shared my minecraftWorlds folder to my NAS. From there, I attempted to share it with my pc, which is running syncthing 1.29.4. Even after I gave SyncthingServiceAcct full permissions for the target folder “%localappdata%\Packages\Microsoft.MinecraftUWP_8wekyb3d8bbwe\LocalState\games\com.mojang\minecraftWorlds”, It displays that the folder is synced, but does not write to the folder. I’m not quite sure where to go from here.
This is my log after a restart, and attempting to share the folder from both my phone and my NAS
2025-04-11 13:45:15 Established secure connection to 4ONNUZH at [fd24:96a0:bcf5:e2ee:34a7:413a:e8af:7840]:22000-[fd24:96a0:bcf5:e2ee:50a0:a09a:d080:9d89]:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-61LAIKF4H10H0FBATR1C62Q3RI 2025-04-11 13:45:15 Device 4ONNUZH client is “syncthing v1.28.1” named “Pixel 7” at [fd24:96a0:bcf5:e2ee:34a7:413a:e8af:7840]:22000-[fd24:96a0:bcf5:e2ee:50a0:a09a:d080:9d89]:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-61LAIKF4H10H0FBATR1C62Q3RI 2025-04-11 13:45:16 Unexpected folder “Minecraft Worlds” (f9uhe-pjwma) sent from device “HLYPTRP-LC5Y2ZP-HICUFWD-2VRQLVB-KVPKZAX-ZK7JCPA-4A52JU7-JAURLA7”; ensure that the folder exists and that this device is selected under “Share With” in the folder configuration. 2025-04-11 13:45:18 Unexpected folder “Minecraft Worlds” (f9uhe-pjwma) sent from device “4ONNUZH-K7OVHLW-EDEPH6H-INLMO3T-QKTMFUY-JFAKGHX-G62SKYW-22MIPQQ”; ensure that the folder exists and that this device is selected under “Share With” in the folder configuration. 2025-04-11 13:45:24 Adding folder “Minecraft Worlds” (f9uhe-pjwma) 2025-04-11 13:45:24 No stored folder metadata for “f9uhe-pjwma”; recalculating 2025-04-11 13:45:24 Ready to synchronize “Minecraft Worlds” (f9uhe-pjwma) (sendreceive) 2025-04-11 13:45:24 Device 4ONNUZH folder “Minecraft Worlds” (f9uhe-pjwma) has mismatching index ID for us (0xCB04B9DB94AB159E != 0xBA9BD317D2AABA81) 2025-04-11 13:45:24 Device 4ONNUZH folder “Minecraft Worlds” (f9uhe-pjwma) has a new index ID (0x39B9B31A784BAB6C) 2025-04-11 13:45:24 Completed initial scan of sendreceive folder “Minecraft Worlds” (f9uhe-pjwma) 2025-04-11 13:45:30 Joined relay relay://141.11.213.195:22067 2025-04-11 13:45:35 Detected 0 NAT services 2025-04-11 13:45:55 Ready to synchronize “Minecraft Worlds” (f9uhe-pjwma) (sendreceive) 2025-04-11 13:45:55 Restarted folder “Minecraft Worlds” (f9uhe-pjwma) (sendreceive) 2025-04-11 13:45:55 Index for nonexistent or paused folder “f9uhe-pjwma” 2025-04-11 13:45:55 Lost primary connection to HLYPTRP at [::]:22000-192.168.86.173:22000/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P20-61LAIKGM2A59UCRB6TDISIMOAQ: handling index for f9uhe-pjwma: f9uhe-pjwma: no such folder (0 remain) 2025-04-11 13:45:55 Connection to HLYPTRP at [::]:22000-192.168.86.173:22000/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P20-61LAIKGM2A59UCRB6TDISIMOAQ closed: handling index for f9uhe-pjwma: f9uhe-pjwma: no such folder 2025-04-11 13:45:55 Completed initial scan of sendreceive folder “Minecraft Worlds” (f9uhe-pjwma) 2025-04-11 13:45:55 Established secure connection to HLYPTRP at 192.168.86.250:22000-192.168.86.173:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-61LAIP77S8GJG13FCC7OBPJ0CU 2025-04-11 13:45:55 Device HLYPTRP client is “syncthing v1.29.4” named “goobtube” at 192.168.86.250:22000-192.168.86.173:22000/tcp-server/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-61LAIP77S8GJG13FCC7OBPJ0CU 2025-04-11 13:45:56 Device HLYPTRP folder “Minecraft Worlds” (f9uhe-pjwma) has a new index ID (0x50060BD1529D43D5)
The log contains info about two different devices trying to connect. It’s not quite consistent, but the folder seems to not have been accepted on the device where you grabbed the log. Then again it is added locally.
Please provide more details on what is shared with which device (screenshots from the GUI help a lot) and explain what you were doing while that log was recorded.