S3Drive - Android - Missing sync configs

Hi @Tom, Usually, at least once per day, I get the following error on a sync task with an S3 bucket:

Last error: Missing sync config, please setup profile again or click: 'Rclone remote' in the 'Account settings'.

#22 Sync failed. Exception: didn't find section in config file ("s3drive_enc_Bucket"). Stack: * * * * * * * * * * * * * * * *
pid: 28029, tid: 482221940888, name 6.ui
os: android arch: arm64 comp: yes sim: no
build_id: '4f1bdaeddcaca841128a5ff37872a6aa'
isolate_dso_base: 6bee84d000, vm_dso_base: 6bee84d000
isolate_instructions: 6beec53940, vm_instructions: 6beec3d000
    #00 abs 0000006beed20d57 virt 00000000004d3d57 _kDartIsolateSnapshotInstructions+0xcd417
    #01 abs 0000006bef56d40b virt 0000000000d2040b _kDartIsolateSnapshotInstructions+0x919acb
<asynchronous suspension>
    #02 abs 0000006bef6538cb virt 0000000000e068cb _kDartIsolateSnapshotInstructions+0x9fff8b
<asynchronous suspension>
    #03 abs 0000006bef66bb0f virt 0000000000e1eb0f _kDartIsolateSnapshotInstructions+0xa181cf
<asynchronous suspension>
    #04 abs 0000006bef5aa663 virt 0000000000d5d663 _kDartIsolateSnapshotInstructions+0x956d23
<asynchronous suspension>
    #05 abs 0000006bef68dea7 virt 0000000000e40ea7 _kDartIsolateSnapshotInstructions+0xa3a567
<asynchronous suspension>

The fixes mentioned in the first line of the error are only temporary. I have multiple S3 accounts and sync tasks set up, and in some cases I use the same bucket with different credentials. Also, when I set a custom name for an S3 account, it does not update in already existing sync tasks. Could you please look into this? Thanks in advance. Wishing you a Merry Christmas and a Happy New Year.

(edited)

I haven't got a single notification about failed update during holidays and it end up like on the screenshot. Unfortunately, with this behavior is the app unusable for me.

Hi @FunnyMarty, Sorry for not getting back to you earlier and Happy New Year!

Also, when I set a custom name for an S3 account, it does not update in already existing sync tasks.

That's a current limitation which we're aware. As far I am concerned there is a relevant prompt that says that user needs to rename all references. We will improve that in the future.

Last error: Missing sync config, please setup profile again or click: 'Rclone remote' in the 'Account settings'.

This error would normally appear after rename, since Sync config would point to old name. As mentioned above, that's current app limitation -> it is required to update Sync after rename. Since you say:

Usually, at least once per day

It seems to be some other issue. Is that external S3 or S3Drive storage? Do you use custom name? (edited)

Tom

Hi @FunnyMarty, Sorry for not getting back to you earlier and Happy New Year!

Also, when I set a custom name for an S3 account, it does not update in already existing sync tasks.

That's a current limitation which we're aware. As far I am concerned there is a relevant prompt that says that user needs to rename all references. We will improve that in the future.

Last error: Missing sync config, please setup profile again or click: 'Rclone remote' in the 'Account settings'.

This error would normally appear after rename, since Sync config would point to old name. As mentioned above, that's current app limitation -> it is required to update Sync after rename. Since you say:

Usually, at least once per day

It seems to be some other issue. Is that external S3 or S3Drive storage? Do you use custom name? (edited)

Hi @Tom, I set custom names at the beginning and usually don't change them; but when I do, I update my sync tasks as I'm aware that otherwise the Sync won't work. I tried removing the custom name and updating the sync task, but this problem occurs regardless of whether a custom name is set or not. I use external S3 (Backblaze) on a Samsung device running Android 16 with the latest S3Drive (which is mostly running in the background). I have also noticed that this mostly happens on my phone rather than on my tablet, which has the same Android version and brand, but doesn't switch networks from Wi-Fi to cellular. I don't know if this could have an impact, but I rather mention it because it's the only difference I've noticed. (edited)

FunnyMarty

Hi @Tom, I set custom names at the beginning and usually don't change them; but when I do, I update my sync tasks as I'm aware that otherwise the Sync won't work. I tried removing the custom name and updating the sync task, but this problem occurs regardless of whether a custom name is set or not. I use external S3 (Backblaze) on a Samsung device running Android 16 with the latest S3Drive (which is mostly running in the background). I have also noticed that this mostly happens on my phone rather than on my tablet, which has the same Android version and brand, but doesn't switch networks from Wi-Fi to cellular. I don't know if this could have an impact, but I rather mention it because it's the only difference I've noticed. (edited)

Yesterday, it happened right after I turned off the Wi-Fi on my phone and triggered a manual sync.

FunnyMarty

Yesterday, it happened right after I turned off the Wi-Fi on my phone and triggered a manual sync.

Wait, so you've turned off the Wi-Fi and then went to Sync tab to run the sync? Was it just for test purposes or you wanted to run Sync on mobile connection?

At that moment, it was for testing purposes, but usually, my phone automatically syncs over a cellular connection. I had to turn off the Wi-Fi for another reason, and it occurred to me to try this. I saw that the last sync had been successful on Wi-Fi, and when I triggered a manual sync on cellular, the error popped up. Then I had to click 'Rclone remote' in the 'Account settings' to make the sync work again, regardless of the network used, but as I said, this fix is only temporary.

Hi @FunnyMarty, we've made some improvements in our latest Android release. I would appreciate if you could update and let us know if your problem is now resolved.

Tom

Hi @FunnyMarty, we've made some improvements in our latest Android release. I would appreciate if you could update and let us know if your problem is now resolved.

Hi @Tom, unfortunately these improvements have not helped. After switching networks and manually triggering the sync, I first got the error shown below, and then after a few seconds I tried again and got the “Missing sync config” one. (edited)

Hi @Tom, any news on this? This error still occurs multiple times per day for me, and it’s pretty frustrating, because sometimes I don’t even get an error message.

Hi @FunnyMarty, I am sorry, but we still haven't found the exact cause. Can you let me know if you have background sync enabled and if this problem happens as well with background sync disabled? This one is tricky, as it happens intermittently and there are multiple "entry points" where sync is started and we're not exactly sure which one is causing issues. I know it's embarrassing, we're trying to get this resolved, but for some reason it's not as easy as it may seem.

Tom

Hi @FunnyMarty, I am sorry, but we still haven't found the exact cause. Can you let me know if you have background sync enabled and if this problem happens as well with background sync disabled? This one is tricky, as it happens intermittently and there are multiple "entry points" where sync is started and we're not exactly sure which one is causing issues. I know it's embarrassing, we're trying to get this resolved, but for some reason it's not as easy as it may seem.

Hi @Tom, thanks for getting back to me. I have been using the app with background sync turned on the whole time. Occasionally, for some reason, background sync even turned itself off, so I had to turn it back on. I have now turned background sync off and set the app to Keep open in the Android task manager, so we will see how it behaves. I will let you know in a few days.

Hi @Tom, I found that the behavior is similar whether background sync is turned off or on. As soon as the network switches from mobile data to Wi-Fi, or vice versa, the config is missing. I also found that recently this only happens with job that synchronizes many different file types. Another job that synchronizes only JPEG and MP4 files does not show this error. I hope this information will be useful to you.

FunnyMarty

Hi @Tom, I found that the behavior is similar whether background sync is turned off or on. As soon as the network switches from mobile data to Wi-Fi, or vice versa, the config is missing. I also found that recently this only happens with job that synchronizes many different file types. Another job that synchronizes only JPEG and MP4 files does not show this error. I hope this information will be useful to you.

Thanks for that. Are there any differences between these two jobs except the file types? E.g. different folder depth or perhaps S3 (for one), Rclone (for another)... or perhaps are these two syncing to same back-end?

Tom

Thanks for that. Are there any differences between these two jobs except the file types? E.g. different folder depth or perhaps S3 (for one), Rclone (for another)... or perhaps are these two syncing to same back-end?

Both jobs use different S3 buckets on Backblaze (the buckets have the same settings). The failing job syncs from the 4th nested local folder into a folder on its remote, while the working one copies from the 5th nested local folder to the root of its remote. Both accounts were added via the S3 compatible option. The File watcher is off. Let me know if you need any more info.

Hi @FunnyMarty, we've pinpointed potential place where the issue could happen. Even though we can't reproduce the problem reliably, we hope that this fix would address issue that you're experiencing. We plan to include a fix in a next release. Will let you know once it's deployed. (edited)

1

It’s now live on Google Play, would appreciate your feedback on this update. Thanks

Hi @Tom, after downloading the update I've monitored it for a few days, and unfortunately it now seems a bit worse, as the issue has started occurring even without switching networks. I currently have the app set to use only mobile data and background sync is enabled. As for notifications, I have the app’s battery mode set to unrestricted, but I've not received the sync error notification until I manually opened the app. Thanks, and let me know if you need any additional information.

Not a great news, but thanks for the update. There is still one more place we need to check and even though it's slightly blind-work I hope we're able to nail that down.