[GH-ISSUE #1519] Moving bookmarks.xbel to another Google Drive Account doesn't read the existing file and creates a new one instead #1001

Closed
opened 2026-02-25 22:38:41 +03:00 by kerem · 4 comments
Owner

Originally created by @zavocc on GitHub (Jan 13, 2024).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1519

Which version of floccus are you using?

5.0.9

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.

Chrome 120.0.6099.217

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

N/A

Which version of Nextcloud? (if relevant)

N/A

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

N/A

Describe the Bug

I've been transferring my bookmarks.xbel file to another google drive account, if I logged in to the new browser profile from scratch with alternative google drive account and try to login with it with the floccus extension (without importing profiles). It just creates a new bookmarks.xbel file instead of reading the existing file in Google Drive.

Expected Behavior

I would expect for it to pull my bookmarks from that file

To Reproduce

  1. On the browser profile with the bookmarks data with old google account where Floccus is currently syncing, download the existing bookmarks.xbel file
  2. Create a new profile in Chrome or chromium derivatives
  3. Login to the new or alternate google account and place the copied bookmarks.xbel to that alternative account in the same location as the old account
  4. Login with Google in the Floccus setup page without importing profiles and configure where to sync as usual (e.g. in specific folder where bookmarks have been pulled and sync from there)
  5. Run sync and observe google drive, you will see a new file is created instead rather than using existing ones

Debug log provided

  • I have provided a debug log file
Originally created by @zavocc on GitHub (Jan 13, 2024). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1519 ### Which version of floccus are you using? 5.0.9 ### 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. Chrome 120.0.6099.217 ### Which version of Nextcloud Bookmarks are you using? (if relevant) N/A ### Which version of Nextcloud? (if relevant) N/A ### What kind of WebDAV server are you using? (if relevant) N/A ### Describe the Bug I've been transferring my bookmarks.xbel file to another google drive account, if I logged in to the new browser profile from scratch with alternative google drive account and try to login with it with the floccus extension (without importing profiles). It just creates a new bookmarks.xbel file instead of reading the existing file in Google Drive. ### Expected Behavior I would expect for it to pull my bookmarks from that file ### To Reproduce 1. On the browser profile with the bookmarks data with old google account where Floccus is currently syncing, download the existing bookmarks.xbel file 2. Create a new profile in Chrome or chromium derivatives 3. Login to the new or alternate google account and place the copied bookmarks.xbel to that alternative account in the same location as the old account 4. Login with Google in the Floccus setup page without importing profiles and configure where to sync as usual (e.g. in specific folder where bookmarks have been pulled and sync from there) 5. Run sync and observe google drive, you will see a new file is created instead rather than using existing ones ### Debug log provided - [ ] I have provided a debug log file
kerem 2026-02-25 22:38:41 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@github-actions[bot] commented on GitHub (Jan 13, 2024):

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.
I'm Marcel and I created floccus and have been maintaining it ever 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.
Note also that GitHub 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!
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 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.

I look forward to working with you on this issue
Cheers 💙

<!-- gh-comment-id:1890238396 --> @github-actions[bot] commented on GitHub (Jan 13, 2024): 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. I'm Marcel and I created floccus and have been maintaining it ever 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. Note also that GitHub 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! 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 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. I look forward to working with you on this issue Cheers :blue_heart:
Author
Owner

@zavocc commented on GitHub (Jan 13, 2024):

Workaround seems to be by just replacing the newly created bookmarks.xbel file with the old one, since Google might have given different scoped access to particular file which it couldn't read the old bookmarks.xbel file, i believe this wouldn't be the case for webdav or other storage provider without special file access

<!-- gh-comment-id:1890451285 --> @zavocc commented on GitHub (Jan 13, 2024): Workaround seems to be by just replacing the newly created bookmarks.xbel file with the old one, since Google might have given different scoped access to particular file which it couldn't read the old bookmarks.xbel file, i believe this wouldn't be the case for webdav or other storage provider without special file access
Author
Owner

@marcelklehr commented on GitHub (Jan 27, 2024):

Indeed, the Google Drive permissions floccus requests are to read only files that it created itself.

<!-- gh-comment-id:1913162068 --> @marcelklehr commented on GitHub (Jan 27, 2024): Indeed, the Google Drive permissions floccus requests are to read only files that it created itself.
Author
Owner

@github-actions[bot] commented on GitHub (Jan 27, 2025):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

<!-- gh-comment-id:2614657826 --> @github-actions[bot] commented on GitHub (Jan 27, 2025): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
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#1001
No description provided.