starred/floccus

Fork 0

mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-25 14:16:12 +03:00

[GH-ISSUE #2086] Helium Browser #1397

New issue

Closed

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 @rasmusjosefsson-outreach on GitHub (Oct 29, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2086

Which version of floccus are you using?

5.7.0

How many bookmarks do you have, roughly?

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

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.

Helium

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

Trying to setup sync with Google Drive, getting following error:

Access blocked: Authorization Error

You can't sign in to this app because it doesn't comply with Google's OAuth 2.0 policy for keeping apps secure.

You can let the app developer know that this app doesn't comply with one or more Google validation rules.
Learn more about this error
If you are a developer of floccus bookmark sync, see error details.
Error 400: invalid_request

Expected Behavior

Should be able to sync with google drive

To Reproduce

Download latest helium browser
Add Floocus extenssion
Try to sync with google drive, login fails to google with error

Debug log provided

I have provided a debug log file

Originally created by @rasmusjosefsson-outreach on GitHub (Oct 29, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2086 ### Which version of floccus are you using? 5.7.0 ### How many bookmarks do you have, roughly? 10 ### 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. Helium ### 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 Trying to setup sync with Google Drive, getting following error: Access blocked: Authorization Error You can't sign in to this app because it doesn't comply with Google's OAuth 2.0 policy for keeping apps secure. You can let the app developer know that this app doesn't comply with one or more Google validation rules. [Learn more about this error](https://developers.google.com/identity/protocols/oauth2/policies#secure-response-handling) If you are a developer of floccus bookmark sync, see error details. Error 400: invalid_request ### Expected Behavior Should be able to sync with google drive ### To Reproduce 1. Download latest helium browser 2. Add Floocus extenssion 3. Try to sync with google drive, login fails to google with error ### 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

kerem commented

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

Author

Owner

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

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

kerem commented

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

Author

Owner

@pacassa commented on GitHub (Nov 9, 2025):

I have exctly the same problem

@pacassa commented on GitHub (Nov 9, 2025): I have exctly the same problem

kerem commented

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

Author

Owner

@Avadhut09 commented on GitHub (Nov 26, 2025):

Same issue about Authorization Error with floccus on helium browser on my end here.

@Avadhut09 commented on GitHub (Nov 26, 2025): Same issue about Authorization Error with floccus on helium browser on my end here.

kerem commented

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

Author

Owner

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

see #2089

@marcelklehr commented on GitHub (Dec 3, 2025): see #2089

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

No description provided.

Rows
Columns