LibreWolf sync with Git broke with: (intermediate value).includes is not a function

[JeGr]

Which version of floccus are you using?

5.8.6

How many bookmarks do you have, roughly?

~500

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.

LibreWolf 148.0-1

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

Which version of Nextcloud? (if relevant)

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

No response

Describe the Bug

Upon (re)launching the Browser the Addon immediatly goes into X/failed state and shows the following error:

 (intermediate value).includes is not a function | Last synchronized: 1 week ago 

After trying to get it working, restarting, re-adding the configuration, all I got was a minimal debug log:

2026-03-26T13:30:13.072Z Starting sync process for account XYZ
2026-03-26T13:30:13.078Z Calling onSyncStart
2026-03-26T13:30:13.078Z onSyncStart: begin
2026-03-26T13:30:13.078Z (git) init
2026-03-26T13:30:13.088Z Syncing failed with (intermediate value).includes is not a function
2026-03-26T13:30:13.088Z onSyncFail

So it doesn't even start the sync/transmission to git but seems to break beforehand. Restarted, updated all I could but don't get, why it suddenly broke.

Expected Behavior

Syncing worked until recently. I wasn't really on my work PC for a bit more than two weeks because of vacation, before it was just working fine. LibreWolf never made a problem related to it being a Firefox fork or the extension not working.

floccus-5.8.6-2026-03-26-full.log

To Reproduce

Don't know if it can be easily reproduced, for me it's just installing the extension in my current LibreWolf Version, trying to add my GIT setup from before and getting that problem.

Debug log provided

• I have provided a debug log file

[github-actions]

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]

Hi @JeGr
Thank you for taking the time to give feedback! Could you try uninstalling the addon and reinstalling?

[JeGr]

Hi,
no problem. Weirdly enough after removing and reinstalling and importing the jobs again, the exact same error message was presented as before. After removing it yet again and reinstalling I re-did the jobs manually instead of importing and after recreating manually triggered them again. After that, finally it began working again. Weird as it is. But the first remove/reinstall/reimport somehow triggered the exact same error again, it didn't even try to upload or sync but immediately quit with the error above.

After recreating the jobs I tried comparing the export before and after manually recreating it and as far as I saw, they looked the same. So I'm a bit baffled but yeah, completely deleting/killing it and recreating it solved that as weird as it sounds :)

Cheers,
Jens

[marcelklehr]

So I'm a bit baffled but yeah, completely deleting/killing it and recreating it solved that as weird as it sounds :)

Yay, I'm glad that worked. I had a hunch that floccus had some remnants lying around in IndexedDB storage from previous sync runs and those might have messed with the git sync. The upcoming release should remove all such remnants after each sync to prevent this kind of error :)

[marcelklehr]

v5.9.0 is out now