mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 06:06:05 +03:00
[GH-ISSUE #2153] [Orion iOS] Sync takes longer since v5.8.3 #1448
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#1448
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ricklahaye on GitHub (Jan 18, 2026).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2153
Which version of floccus are you using?
5.8.3
How many bookmarks do you have, roughly?
30
Are you using other means to sync bookmarks in parallel to floccus?
No
Sync method
Git
Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.
Orion 1.4.4
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
Floccus 5.8.3 has issues with syncing and stays stuck on 'Sychronization in progress'. Sometimes it does sync succesfully but it can take multiple minutes!
This behaviour is occuring for Git, but also WebDav integration.
Floccus 5.8.2 syncs correctly and finishes within 1-3 seconds.
Expected Behavior
Syncing should finish in few seconds instead of minutes.
To Reproduce
Install Floccus 5.8.3, add profile, and notice that syncthing takes multiple minutes or does not sync at all.
Installl Floccus 5.8.2, and notice that syncing finishes correctly in few seconds.
Debug log provided
@github-actions[bot] commented on GitHub (Jan 18, 2026):
Hello! 👋
Thank you for taking the time to open this issue with floccus. I know it's frustrating when software causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at and if possible solved. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings. I'm Marcel. I created floccus a few years ago, and have been maintaining it since. I currently work for Nextcloud which leaves me with less time for side projects like this one than I used to have. I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it. Until then, please be patient. It helps when you stick around to answer follow up questions I may have, as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report and the issue cannot be solved without it, I will have to close the issue after a while. Note also that GitHub in general is a place where people meet to make software better together. Nobody here is under any obligation to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can collaborate to make this software better. For everyone. Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and try to fix the odd bug yourself. Everyone will be thankful for extra helping hands! If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way, I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already. You can find donation options at https://floccus.org/donate/. Thank you!
One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the Nextcloud forum, to twitter or somewhere else. But this is a technical issue tracker, so please make sure to focus on the tech and keep your opinions to yourself.
Thank you for reading through this primer. I look forward to working with you on this issue! Cheers! 💙
@marcelklehr commented on GitHub (Jan 18, 2026):
Hi @ricklahaye
Thank you for taking the time to give feedback by opening this issue! I'll try to reproduce this and fix it. I have a hunch that this has to do with the optimization I did for the Chrome issue where Chrome was killing the floccus worker due to too long macro tasks in the event loop, now there are smaller macro tasks, but maybe they are too small and are causing an overhead..
@ricklahaye commented on GitHub (Jan 18, 2026):
Thank you. I have another debug log. Weirdly enough the log shows it took a total of 5 seconds. I am very sure that the UI showed sync in progress for way longer than 5 seconds. Seems that the timing in the log is of?
@ricklahaye commented on GitHub (Jan 19, 2026):
With another run today it took around 50 seconds for a sync to complete. The log however shows 5 seconds total again.
@marcelklehr commented on GitHub (Jan 20, 2026):
I can reproduce that sync seems to take longer now.
Where do you check in the UI? Do you check the Icon or the drop down overview panel?
@ricklahaye commented on GitHub (Jan 21, 2026):
I check the status in the blue box in this overview (which I expectt to be drop down overview panel):
@SkyBlueHH commented on GitHub (Jan 30, 2026):
With version 5.8.6, the problem seems to have been solved for most browsers.
However, in my Chromium (unfortunately an older one, on older mac OS), the problem persists in a slightly modified form: after startup, floccus starts synchronizing and the icon changes accordingly.
Unfortunately, the sync never finishes – until I click on the icon and the panel opens. From then on, it only takes the usual few seconds.
@marcelklehr commented on GitHub (Feb 6, 2026):
Mmh, it could be that v5.8.6 is not installed there yet, I'm doing gradual rollouts on Chromium to avoid hitting big issues with 100% of the user base immediately. You can make sure you have the latest version by going to
chrome://extensionsand hitting update.@SkyBlueHH commented on GitHub (Feb 6, 2026):
Due to the problems, I have already made sure that the latest version is installed:
This is what the symbol looked like for more than an hour:
As soon as I click on the icon, the synchronization proceeds as quickly as usual.
Due to the old macOS, it is still Chromium 127 from the Chromium Legacy Project. The issue began with version 5.8.3. Before that, everything was fine. Latest version of Nextcloud on the other side.
@maodun96 commented on GitHub (Feb 6, 2026):
I have the same issue. I freshly installed the 5.8.6 extension on Orion for iPad & iPhone. I tried both the Firefox and Chrome versions, and neither can sync properly. The sync takes a very long time and fails. My bookmark file is about 700KB.
I reinstalled the 5.8.2 Firefox extension, and everything is working normally again.
@marcelklehr commented on GitHub (Feb 6, 2026):
Hi @maodun96
Thank you for chiming in with this similar issue!
What do you mean by it fails? Do you get an error message?
@maodun96 commented on GitHub (Feb 6, 2026):
Hi @marcelklehr
The progress bar never actually completes; occasionally, it shows as finished when I reopen the extension.
Most of the time when I open it, the progress bar remains incomplete.
No error messages are received on the extension page. (But I haven’t downloaded the logs to check.)
In version 5.8.2, synchronization usually completed within tens of seconds. So in version 5.8.6, I can clearly sense the anomaly: after two or three minutes, the progress bar advances but never completes.
@marcelklehr commented on GitHub (Feb 6, 2026):
mmmh, I have a hunch where this might be coming from: In v5.8.3 I fixed the issue that chrome was often killing the sync process mid-way through because the code was running the whole sync in one macro task which apparently was running too long for chrome's taste. My solution for this was to add intermittent setTimeout calls to start new macro tasks during the sync. I suspect that older Chrome versions and Orion may not like this :/
@marcelklehr commented on GitHub (Feb 6, 2026):
@maodun96 Which sync method are you using? Git as well? With Nc Bookmarks, floccus works for me on the latest Orion for Mac. Or does this only happen on iOS for you?
@ricklahaye commented on GitHub (Feb 6, 2026):
I originally only had the issue with Orion on iOS. I tried sync method Git and Webdav, and both had same issue that it was very low.
@maodun96 commented on GitHub (Feb 6, 2026):
WEBDAV, this issue occurs on both iPadOS and iOS. I don't use my Mac very often.
@merlinpimpim commented on GitHub (Feb 11, 2026):
Hello,
Similar problem. But it's more a problem with the size of the index than the time it takes to synchronize, actually.
I received version 5.8.6 yesterday and was obviously on version 5.8.3 just before that:
The problem since version 5.8.6 is as follows:
I had to disable security for the synchronization to start:
After synchronization, the .xbel file was much larger (which probably explains the longer synchronization times):
7 MB more!
Is this expected behavior (larger index) or is there a bug?
It's important to know because I have another PC with Chrome that is still on version 5.8.3, and there is some kind of conflict between the sizes of these two versions when they try to synchronize.
Should I force my second PC to upgrade to 5.8.6, or is there a problem with version 5.8.6 (or an intermediate version)?
nb: I use Webdav and have over 60k bookmarks.
Thank you.
@marcelklehr commented on GitHub (Feb 13, 2026):
Hello @merlinpimpim
Your issue seems unrelated. v5.8.6 does not cause larger bookmark files. The larger file is a direct consequence of the 14% increase in bookmarks count that the failsafe warned about. If you did not recently add many bookmarks then you've hit a bug. It will be hard to figure out after the fact why this happened, though :/ Could you open a new issue for this, please?
@merlinpimpim commented on GitHub (Feb 13, 2026):
#2173