[GH-ISSUE #2114] Cannot read properties of undefined (reading 'filter') #1419

Open
opened 2026-02-25 22:39:58 +03:00 by kerem · 5 comments
Owner

Originally created by @avitubaros1 on GitHub (Dec 8, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2114

Which version of floccus are you using?

5.8.0

How many bookmarks do you have, roughly?

5k

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.

Brave 1.84.141

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

Getting Cannot read properties of undefined (reading 'filter') error when trying to sync
floccus-5.8.0-2025-12-08-full (2).log

Expected Behavior

Syncing successfully without an error

To Reproduce

Just sync

Debug log provided

  • I have provided a debug log file
Originally created by @avitubaros1 on GitHub (Dec 8, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2114 ### Which version of floccus are you using? 5.8.0 ### How many bookmarks do you have, roughly? 5k ### 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. Brave 1.84.141 ### 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 Getting Cannot read properties of undefined (reading 'filter') error when trying to sync [floccus-5.8.0-2025-12-08-full (2).log](https://github.com/user-attachments/files/24036508/floccus-5.8.0-2025-12-08-full.2.log) ### Expected Behavior Syncing successfully without an error ### To Reproduce Just sync ### Debug log provided - [x] I have provided a debug log file
Author
Owner

@github-actions[bot] commented on GitHub (Dec 8, 2025):

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! 💙

<!-- gh-comment-id:3627672621 --> @github-actions[bot] commented on GitHub (Dec 8, 2025): Hello! :wave: 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! :blue_heart:
Author
Owner

@marcelklehr commented on GitHub (Dec 13, 2025):

Hi @avitubaros1
Thank you for taking the time to give feedback by opening this issue!
This error shouldn't happen, I also cannot reproduce it offhand. Could you try updating brave to the latest version (1.85, I believe)? Oh, and is this your first time using floccus, or has this worked for you before?

<!-- gh-comment-id:3649149595 --> @marcelklehr commented on GitHub (Dec 13, 2025): Hi @avitubaros1 Thank you for taking the time to give feedback by opening this issue! This error shouldn't happen, I also cannot reproduce it offhand. Could you try updating brave to the latest version (1.85, I believe)? Oh, and is this your first time using floccus, or has this worked for you before?
Author
Owner

@avitubaros1 commented on GitHub (Dec 14, 2025):

@marcelklehr Thank you for your help.
I updated the brave browser to latest version (Brave 1.85.116 (Official Build) (arm64)) and unfortunately it is still happening.
I am using floccus for some time (over a year I think) but the error started only recently (couple of weeks I think)

<!-- gh-comment-id:3650656921 --> @avitubaros1 commented on GitHub (Dec 14, 2025): @marcelklehr Thank you for your help. I updated the brave browser to latest version (Brave 1.85.116 (Official Build) (arm64)) and unfortunately it is still happening. I am using floccus for some time (over a year I think) but the error started only recently (couple of weeks I think)
Author
Owner

@marcelklehr commented on GitHub (Dec 14, 2025):

Could it be that you have set up multiple profiles for the same local folder without allowing nested sync in the settings for both?

<!-- gh-comment-id:3651067288 --> @marcelklehr commented on GitHub (Dec 14, 2025): Could it be that you have set up multiple profiles for the same local folder without allowing nested sync in the settings for both?
Author
Owner

@avitubaros1 commented on GitHub (Dec 16, 2025):

I have only one profile, and also the nested sync is enable (don't know if that has an effect on a single profile)
Image
I also notice that my extension is in version 5.8.0 and not the latest github release because that is the version in the store. Don't know if this is intentional.

<!-- gh-comment-id:3660014205 --> @avitubaros1 commented on GitHub (Dec 16, 2025): I have only one profile, and also the nested sync is enable (don't know if that has an effect on a single profile) <img width="593" height="466" alt="Image" src="https://github.com/user-attachments/assets/16f77e18-5391-4681-9f30-91379c2c830f" /> I also notice that my extension is in version 5.8.0 and not the latest github release because that is the version in the [store](https://chromewebstore.google.com/detail/floccus-bookmarks-sync/fnaicdffflnofjppbagibeoednhnbjhg). Don't know if this is intentional.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/floccus#1419
No description provided.