[GH-ISSUE #2044] Syncing Root folder between Chrome <138 and Chrome >= 138 #1366

Closed
opened 2026-02-25 22:39:48 +03:00 by kerem · 7 comments
Owner

Originally created by @ForeverInfinity on GitHub (Aug 29, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2044

Which version of floccus are you using?

5.6.0

How many bookmarks do you have, roughly?

200-300

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

Yes, I sync bookmarks on Chrome and Edge through my Google account and MS account respectively

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.

Edge 139

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

I don't know this

Which version of Nextcloud? (if relevant)

I don't know this

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

No response

Describe the Bug

My Chrome can pull and push bookmarks smoothly, but Edge has been unable to sync bookmarks for the past two weeks. I tried to clear the local bookmarks and try to pull again, but I got a blank bookmark folder.

floccus-5.6.0-2025-08-29-redacted.log

Expected Behavior

The bookmarks I stored in Google Drive should appear in Edge Favorites

To Reproduce

I exported a profile from Chrome and imported it into Edge, then immediately manually synced my favorites, but my bookmarks didn't appear in my favorites as expected.

Debug log provided

  • I have provided a debug log file
Originally created by @ForeverInfinity on GitHub (Aug 29, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2044 ### Which version of floccus are you using? 5.6.0 ### How many bookmarks do you have, roughly? 200-300 ### Are you using other means to sync bookmarks in parallel to floccus? Yes, I sync bookmarks on Chrome and Edge through my Google account and MS account respectively ### 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. Edge 139 ### Which version of Nextcloud Bookmarks are you using? (if relevant) I don't know this ### Which version of Nextcloud? (if relevant) I don't know this ### What kind of WebDAV server are you using? (if relevant) _No response_ ### Describe the Bug My Chrome can pull and push bookmarks smoothly, but Edge has been unable to sync bookmarks for the past two weeks. I tried to clear the local bookmarks and try to pull again, but I got a blank bookmark folder. [floccus-5.6.0-2025-08-29-redacted.log](https://github.com/user-attachments/files/22036519/floccus-5.6.0-2025-08-29-redacted.log) ### Expected Behavior The bookmarks I stored in Google Drive should appear in Edge Favorites ### To Reproduce I exported a profile from Chrome and imported it into Edge, then immediately manually synced my favorites, but my bookmarks didn't appear in my favorites as expected. ### Debug log provided - [x] I have provided a debug log file
kerem 2026-02-25 22:39:48 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@github-actions[bot] commented on GitHub (Aug 29, 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:3235539590 --> @github-actions[bot] commented on GitHub (Aug 29, 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 (Aug 29, 2025):

Hi @ForeverInfinity
Could you check in your Edge Browser the following URL: edge://version/ to see which chromium version your Edge version is based on? Also, could you find out the version of Chrome you are using?

<!-- gh-comment-id:3237090602 --> @marcelklehr commented on GitHub (Aug 29, 2025): Hi @ForeverInfinity Could you check in your Edge Browser the following URL: `edge://version/` to see which chromium version your Edge version is based on? Also, could you find out the version of Chrome you are using?
Author
Owner

@ForeverInfinity commented on GitHub (Aug 29, 2025):

Hi @ForeverInfinity Could you check in your Edge Browser the following URL: edge://version/ to see which chromium version your Edge version is based on? Also, could you find out the version of Chrome you are using?

This is my version page
Image

<!-- gh-comment-id:3237120937 --> @ForeverInfinity commented on GitHub (Aug 29, 2025): > Hi [@ForeverInfinity](https://github.com/ForeverInfinity) Could you check in your Edge Browser the following URL: `edge://version/` to see which chromium version your Edge version is based on? Also, could you find out the version of Chrome you are using? This is my version page <img width="1665" height="343" alt="Image" src="https://github.com/user-attachments/assets/9f686c6a-9985-4149-ae42-a491082552c5" />
Author
Owner

@marcelklehr commented on GitHub (Aug 29, 2025):

And which version of chrome are you using on the other device that you were talking about that works?

<!-- gh-comment-id:3237406312 --> @marcelklehr commented on GitHub (Aug 29, 2025): And which version of chrome are you using on the other device that you were talking about that works?
Author
Owner

@ForeverInfinity commented on GitHub (Aug 29, 2025):

This is my chrome version, the plugin works fine
Image

<!-- gh-comment-id:3237464359 --> @ForeverInfinity commented on GitHub (Aug 29, 2025): This is my chrome version, the plugin works fine <img width="1619" height="336" alt="Image" src="https://github.com/user-attachments/assets/dc4606b2-cc88-497f-bcfb-f141a874955b" />
Author
Owner

@marcelklehr commented on GitHub (Aug 29, 2025):

Ah, there's the issue. You're using Cent Browser which is based on Chrome 132 under the hood, while Edge uses Chrome 139.

Basically, you can either

  1. choose to sync the Toolbar and the Other bookmarks folder separately in floccus by creating two profiles, one for each, instead of creating one profile for the root folder. This way you can sync browsers from before Chrome 138 with browser after Chrome 138.
  2. or you can choose to only use Browsers that are all based on either Chrome <138 or all based on Chrome >= 138.

Syncing the root folder from a browser with Chrome <138 to a browser with Chrome >=138 doesn't work due to a change in how Chrome exposes bookmarks to extensions.

<!-- gh-comment-id:3237518498 --> @marcelklehr commented on GitHub (Aug 29, 2025): Ah, there's the issue. You're using Cent Browser which is based on Chrome 132 under the hood, while Edge uses Chrome 139. Basically, you can either 1. choose to sync the Toolbar and the Other bookmarks folder separately in floccus by creating two profiles, one for each, instead of creating one profile for the root folder. This way you can sync browsers from before Chrome 138 with browser after Chrome 138. 2. or you can choose to only use Browsers that are *all* based on either Chrome <138 or *all* based on Chrome >= 138. Syncing the root folder from a browser with Chrome <138 to a browser with Chrome >=138 doesn't work due to a change in how Chrome exposes bookmarks to extensions.
Author
Owner

@ForeverInfinity commented on GitHub (Aug 29, 2025):

Thanks, I will try your answer

<!-- gh-comment-id:3237534058 --> @ForeverInfinity commented on GitHub (Aug 29, 2025): Thanks, I will try your answer
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#1366
No description provided.