Sync interval not saved

[vaini]

Which version of floccus are you using?

4.19.1

Sync method

Google Drive

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

Firefox v118.0.1 and Microsoft Edge Canary v119.0.2129.0

Which version of Nextcloud Bookmarks are you using? (if relevant)

No response

Which version of Nextcloud? (if relevant)

No response

What kind of WebDAV server are you using? (if relevant)

No response

Describe the Bug

Does not record sync interval change from 15 to 5 minutes

Expected Behavior

The change is stored.

To Reproduce

1. Click on the Floccus icon;
2. Click the down arrow for more options;
3. Click on the gear icon (Options);
4. Click on "Sync behavior";
5. In "Sync Interval" change it to 5 minutes (slide);
6. Scroll the page to the end;
7. Click "Save"

Following these steps, a green sign appears, indicating that the change has been saved, however, when opening the settings screen again, or even restarting the browser, the synchronization interval returns to 15 minutes. The same thing happens in the two browsers I used.

Debug log provided

• I have provided a debug log file

[Rami-Ha]

I'm having the same problem

[exu-g]

I'm also having this issue. Even with a new account, setting the sync interval to 5 minutes doesn't work.

Setting 10 minutes or any greater interval (that I tested) does stick, it appears to be specific to the 5 minutes duration where it will be reset to 15 minutes.
With the 10 minute interval set, it did indeed start a sync about 10 minutes (11 shown in UI) after the previous one.

I couldn't find anything useful in the debug files (redacted or full) searching for words like sync, interval, duration etc. that would give further hints.

For my environment, I'm using Nextcloud 25.13. Freshly set up Floccus today for the first time on two devices (Linux and Windows), both with Firefox 119.

[kolinger]

This issue is duplicate of #1310 that was fixed but not really.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.