Can not create any remote

[arnowelzel]

• I have read the above note

What version of Round Sync are you using (About -> App version)?

2.5.6

What is your Android version, phone model and manufacturer?

Android 17, Google Pixel 6a

Which steps are required to reproduce this issue?

Example:

1. Open the app
2. Go to Remotes
3. Press "+" to add a remote
4. Select SMB and press "->" to continue
5. Enter details
6. Press the "Save" button
7. See the error message as popup - "Error creating remote"

Please also enable rclone logging (Settings > Logging > Log Rclone errors). You're going to need the log for the last question.

What is your configuration (rclone.conf)?

[5d44cd8d-397c-4107-b79b-17f2b6a071e8]
type = alias
remote = /storage/emulated/0

Does the same issue also occur when using the same configuration on a PC or in Termux?

This is not relevant for this issue. It's about the way how the app behaves.

Also it is impossible to get data from the path where the app stores the log since Android/data/de.felixnuesse.extract/files/logs is inside the sandbox of the app and can not be read without root access. If the log should be accessible, it should be written to one of the shared folders Android/obb/... or Android/media/....

[scr4bble]

Android/obb/ is also protected on modern Android, isn’t it? Android/media/ might be a better location for logs that should be directly accessible to users.

For what it’s worth, I was able to open the current log directory using Total Commander on Android. It should also be accessible from a PC when the phone is connected over USB. In my case, though, there were no relevant entries because the explicitly enabled rclone logging appears to be broken. There is a proposed fix awaiting review in #411.

I also opened #414 to improve error visibility directly inside Round Sync and in sync notifications. Together, these changes should address the missing-error problem I ran into in #407.

We’ll need to wait for @newhinton to review them and decide how to proceed.

[arnowelzel]

To be more precise:

• /storage/emulated/0/Android/data/data - private app storage, each folder is only accessible for the respective app. Otherwise only as root or as system app. Also access via USB is usally not possible, maybe using ADB, but I don't think so.
• /storage/emulated/0/Android/data/obb - opaque binary blob, usually used by apps to keep additional assets which get downloaded after the app installation. At least Google Pixel devices also allow access to this folder since it is not intended to keep private data which must not be accessible by other apps. Apps just need the correct permission for it.
• /storage/emulated/0/Android/data/media - shared media, usually used by apps to store media which can be shared with other apps. This folder is usually always accessible and not protected. Apps just need the correct permission for it.

[scr4bble]

Ok, Samsung Galaxy probably uses slightly different layout.

[arnowelzel]

Maybe this helps: https://developer.android.com/training/data-storage/shared