starred/floccus

Fork 0

mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-25 06:06:05 +03:00

[GH-ISSUE #2089] Nextcloud Bookmark sync fails on Helium browser #1400

New issue

Open

opened 2026-02-25 22:39:54 +03:00 by kerem · 4 comments

kerem commented

2026-02-25 22:39:54 +03:00

Owner

Originally created by @Askanor on GitHub (Nov 1, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2089

Which version of floccus are you using?

5.7.0

How many bookmarks do you have, roughly?

329

Are you using other means to sync bookmarks in parallel to floccus?

Sync method

Nextcloud Bookmarks

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

Helium Version 0.5.8.1 (Official Build, Chromium 141.0.7390.122) (64-bit) on Windows 11

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

15.2.0

Which version of Nextcloud? (if relevant)

31.0.8

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

No response

Describe the Bug

After a successful initial sync on a fresh Helium installation, the automatic sync failed. The log reads: Syncing failed with Cannot read properties of undefined (reading 'children'). Subsequent manual syncs wouldn't start, or at least they generated no new logs. Completely removing Helium and reinstalling Helium and Floccus gave the same result.

Expected Behavior

Since Helium is Chromium-based, I would expect Floccus to sync like it does in other Chromium-based browsers.

To Reproduce

Install the latest version of Helium from their homepage, helium.computer.
Install Floccus Extension
Import a profile from another Chromium browser that uses Nextcloud Bookmarks as a storage backend.
Check the configuration to see if the bookmark path and URL look fine.
Start an initial sync.
Turn on auto-sync.

Debug log provided

I have provided a debug log file

Originally created by @Askanor on GitHub (Nov 1, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2089 ### Which version of floccus are you using? 5.7.0 ### How many bookmarks do you have, roughly? 329 ### Are you using other means to sync bookmarks in parallel to floccus? No ### Sync method Nextcloud Bookmarks ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. Helium Version 0.5.8.1 (Official Build, Chromium 141.0.7390.122) (64-bit) on Windows 11 ### Which version of Nextcloud Bookmarks are you using? (if relevant) 15.2.0 ### Which version of Nextcloud? (if relevant) 31.0.8 ### What kind of WebDAV server are you using? (if relevant) _No response_ ### Describe the Bug After a successful initial sync on a fresh Helium installation, the automatic sync failed. The log reads: `Syncing failed with Cannot read properties of undefined (reading 'children')`. Subsequent manual syncs wouldn't start, or at least they generated no new logs. Completely removing Helium and reinstalling Helium and Floccus gave the same result. ### Expected Behavior Since Helium is Chromium-based, I would expect Floccus to sync like it does in other Chromium-based browsers. ### To Reproduce 1. Install the latest version of Helium from their homepage, helium.computer. 2. Install Floccus Extension 3. Import a profile from another Chromium browser that uses Nextcloud Bookmarks as a storage backend. 4. Check the configuration to see if the bookmark path and URL look fine. 5. Start an initial sync. 6. Turn on auto-sync. ### Debug log provided - [ ] I have provided a debug log file

kerem added the

bug

upstream

browser-specific

labels

2026-02-25 22:39:54 +03:00

kerem commented

2026-02-25 22:39:55 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Nov 1, 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! 💙

@github-actions[bot] commented on GitHub (Nov 1, 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:

kerem commented

2026-02-25 22:39:55 +03:00

Author

Owner

@grimloch commented on GitHub (Nov 11, 2025):

I've been getting this same error in Brave and so far I've been able to "fix" the error by clicking the "Pull down once" arrow in the Floccus icon options at the top of the browser.

@grimloch commented on GitHub (Nov 11, 2025): I've been getting this same error in Brave and so far I've been able to "fix" the error by clicking the "Pull down once" arrow in the Floccus icon options at the top of the browser.

kerem commented

2026-02-25 22:39:55 +03:00

Author

Owner

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

This is likely a Helium issue

@marcelklehr commented on GitHub (Dec 15, 2025): This is likely a Helium issue

kerem commented

2026-02-25 22:39:55 +03:00

Author

Owner

@Mayurifag commented on GitHub (Jan 2, 2026):

There are actually 2 problems of floccus related to Helium browser (or maybe Thorium, I tested a couple weeks ago).

Google Drive sync in floccus done via some internal browser kung-fu, requiring google setup, which was cut in some patches of helium and similar projects. Thats known issue. That does not mean it's impossible to make from scratch this feature without using any browser API, but nobody would bother for minorities using these pesky browsers.
My experience was that floccus made something wrong in Helium/Thorium during backup. It kinda bugged and duplicated some things so it required me to use ChatGPT to fix bookmarks.xbel of floccus. Actually, when I used linkwarden sync, same problem appeared, so it doesnt matter on sync provider.

So, how did it look.. Let's say I have "Bookmarks bar" and "Other bookmarks" with some entities there, regular usage. But when I tried to backup those using floccus, it silently bugged and file had duplicated those folders (so it was 4 folders in backup, 2 normal ones and 2 empty folders with the same names as normal ones), but kinda different hierarchy. As it is bugged, the Import mechanism cant work on this type of problemmed file and also silently fails - the only error was in Console.

Problem was simiar which OP describes.

As Helium user I beg the maintainers to look at this problem. We dont have any sync app to use for syncing bookmarks with other systems or another browsers and floccus left as the only option nowadays and semm not to work with us. I am not very bothered with 1st issue, but 2nd issue makes floccus unusable on Helium and probably some other browsers.

@marcelklehr even though the problem does not reproduce on major browsers, I can't say the browser is the only problem. If it's possible, may the issue be moved from "On Hold"? Thanks in advance! 😄

btw I did not test Nextcloud Bookmark, I have tested webdav, google drive and linkwarden (doesnt matter anyway, problem reproduces everywhere).

@Mayurifag commented on GitHub (Jan 2, 2026): There are actually 2 problems of floccus related to Helium browser (or maybe Thorium, I tested a couple weeks ago). 1) Google Drive sync in floccus done via some internal browser kung-fu, requiring google setup, which was cut in some patches of helium and similar projects. Thats known issue. That does not mean it's impossible to make from scratch this feature without using any browser API, but nobody would bother for minorities using these pesky browsers. 2) My experience was that floccus made something wrong in Helium/Thorium during backup. It kinda bugged and duplicated some things so it required me to use ChatGPT to fix bookmarks.xbel of floccus. Actually, when I used linkwarden sync, same problem appeared, so it doesnt matter on sync provider. So, how did it look.. Let's say I have "Bookmarks bar" and "Other bookmarks" with some entities there, regular usage. But when I tried to backup those using floccus, it silently bugged and file had duplicated those folders (so it was 4 folders in backup, 2 normal ones and 2 empty folders with the same names as normal ones), but kinda different hierarchy. As it is bugged, the Import mechanism cant work on this type of problemmed file and also silently fails - the only error was in Console. Problem was simiar which OP describes. As Helium user I beg the maintainers to look at this problem. We dont have any sync app to use for syncing bookmarks with other systems or another browsers and floccus left as the only option nowadays and semm not to work with us. I am not very bothered with 1st issue, but 2nd issue makes floccus unusable on Helium and probably some other browsers. @marcelklehr even though the problem does not reproduce on major browsers, I can't say the browser is the only problem. If it's possible, may the issue be moved from "On Hold"? Thanks in advance! 😄 btw I did not test Nextcloud Bookmark, I have tested webdav, google drive and linkwarden (doesnt matter anyway, problem reproduces everywhere).

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#1400

No description provided.

Rows
Columns