[GH-ISSUE #2084] Floccus extension not working on ChatGPT Atlas browser with Google Drive sync #1398

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

Originally created by @cinestill-800T on GitHub (Oct 25, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2084

Which version of floccus are you using?

5.7.0

How many bookmarks do you have, roughly?

30

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

No

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.

ChatGPT Atlas 1.2025.288.15

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)

When using Floccus extension version 5.7.0 with ChatGPT Atlas browser (version 1.2025.288.15) and selecting Google Drive as the sync method, the Google Drive login screen does not transition or redirect, and the extension fails to work properly.

Describe the Bug

I expect the Floccus extension to allow logging into Google Drive and synchronize bookmarks successfully without any issues.

Expected Behavior

  1. Install Floccus extension version 5.7.0 on ChatGPT Atlas browser (version 1.2025.288.15).
  2. Configure Floccus to use Google Drive as the sync method.
  3. Attempt to log in to Google Drive through the extension.
  4. Observe that the login page does not transition/redirect and synchronization does not start.

To Reproduce

Describe the Bug: When using Floccus extension version 5.7.0 in ChatGPT Atlas (version 1.2025.288.15) with Google Drive as the sync method, the Google Drive login screen does not transition or redirect, and the extension fails to operate.

Expected Behavior: The extension should allow logging into Google Drive and synchronize bookmarks successfully without any issues.

To Reproduce:

  1. Install Floccus extension version 5.7.0 on ChatGPT Atlas browser (version 1.2025.288.15).
  2. Configure Floccus to use Google Drive as the sync method.
  3. Attempt to log in to Google Drive through the extension.
  4. Observe that the login page does not transition/redirect and synchronization does not start.

Debug log provided

  • I have provided a debug log file
Originally created by @cinestill-800T on GitHub (Oct 25, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2084 ### Which version of floccus are you using? 5.7.0 ### How many bookmarks do you have, roughly? 30 ### Are you using other means to sync bookmarks in parallel to floccus? No ### 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. ChatGPT Atlas 1.2025.288.15 ### 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) When using Floccus extension version 5.7.0 with ChatGPT Atlas browser (version 1.2025.288.15) and selecting Google Drive as the sync method, the Google Drive login screen does not transition or redirect, and the extension fails to work properly. ### Describe the Bug I expect the Floccus extension to allow logging into Google Drive and synchronize bookmarks successfully without any issues. ### Expected Behavior 1. Install Floccus extension version 5.7.0 on ChatGPT Atlas browser (version 1.2025.288.15). 2. Configure Floccus to use Google Drive as the sync method. 3. Attempt to log in to Google Drive through the extension. 4. Observe that the login page does not transition/redirect and synchronization does not start. ### To Reproduce **Describe the Bug:** When using Floccus extension version 5.7.0 in ChatGPT Atlas (version 1.2025.288.15) with Google Drive as the sync method, the Google Drive login screen does not transition or redirect, and the extension fails to operate. **Expected Behavior:** The extension should allow logging into Google Drive and synchronize bookmarks successfully without any issues. **To Reproduce:** 1. Install Floccus extension version 5.7.0 on ChatGPT Atlas browser (version 1.2025.288.15). 2. Configure Floccus to use Google Drive as the sync method. 3. Attempt to log in to Google Drive through the extension. 4. Observe that the login page does not transition/redirect and synchronization does not start. ### Debug log provided - [ ] I have provided a debug log file
kerem 2026-02-25 22:39:54 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@github-actions[bot] commented on GitHub (Oct 25, 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:3445515006 --> @github-actions[bot] commented on GitHub (Oct 25, 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 (Oct 26, 2025):

Hi @cinestill-800T
Thank you for taking the time to give feebdback by reporting this issue here! I appreciate it :)
I think this may be a bug in Atlas, rather than floccus. As a workaround, you can try exporting a fully set up profile from a different browser and import it into floccus in Atlas, that may work.

<!-- gh-comment-id:3448422704 --> @marcelklehr commented on GitHub (Oct 26, 2025): Hi @cinestill-800T Thank you for taking the time to give feebdback by reporting this issue here! I appreciate it :) I think this may be a bug in Atlas, rather than floccus. As a workaround, you can try exporting a fully set up profile from a different browser and import it into floccus in Atlas, that may work.
Author
Owner

@cinestill-800T commented on GitHub (Oct 26, 2025):

Thanks to @marcelklehr's advice, synchronization was successful. I appreciate your help. I also understand that this is an Atlas bug (I have encountered many other issues as well). I hope this thread will be useful for others.

<!-- gh-comment-id:3448584230 --> @cinestill-800T commented on GitHub (Oct 26, 2025): Thanks to @marcelklehr's advice, synchronization was successful. I appreciate your help. I also understand that this is an Atlas bug (I have encountered many other issues as well). I hope this thread will be useful for others.
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#1398
No description provided.