Transferred encrypted folder not recognized by DroidFS (gocryptfs volume fails to open after using LocalSend)

[Alfiant]

I encountered an issue when trying to open an encrypted folder (gocryptfs volume) that was transferred via the LocalSend app.

When I send the same folder via:

• Syncthing ✅ Works fine

• Android’s Quick Share ✅ Works fine

• LocalSend ❌ Fails — DroidFS shows:

“Encrypted volume not recognized. Please check the selected path.”

All files, including gocryptfs.conf, are correctly transferred and visible on the target device. Despite that, DroidFS refuses to open the volume, suggesting that LocalSend may be changing how the files are written to disk.

Steps to Reproduce:

1. Create a gocryptfs (DroidFS) volume on Android device A.

2. Send the folder using LocalSend to Android device B.

3. Try opening the received folder with DroidFS on device B.

4. Observe the error message: “Encrypted volume not recognized.”

5. Repeat the same test using Syncthing or Android Quick Share — volume opens successfully.

Expected Behavior

DroidFS should recognize and open the gocryptfs folder after being transferred with LocalSend, exactly like when it’s copied via Syncthing or Quick Share.

I’m not sure whether this is an issue with DroidFS or LocalSend, but I’m posting it anyway in case it hasn’t been reported yet.

[hardcore-sushi]

If it works with other apps, the issue likely comes from LocalSend. You should maybe open a bug report on their repo.

[hardcore-sushi]

Just tested with LocalSend 1.17.0 and it works fine.

[Alfiant]

Just tested with LocalSend 1.17.0 and it works fine.

Mine is also 1.17.0 on both devices, but it still doesn’t work. However, if I try with another app like ShareIt Lite, it works just fine.