[GH-ISSUE #1963] google drive error #1313

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

Originally created by @universish on GitHub (May 25, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1963

Which version of floccus are you using?

v5.4.5

How many bookmarks do you have, roughly?

1000000+

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.

ungoogled chromium 136.0.7103.113

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

Access denied
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.
Bu hata hakkında daha fazla bilgi
floccus bookmark sync geliştiricilerinden biriyseniz hata ayrıntılarını inceleyin.
Hata 400: invalid_request

Expected Behavior

google won't allow access.

To Reproduce

create new profile
choose google drive

Debug log provided

  • I have provided a debug log file
Originally created by @universish on GitHub (May 25, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1963 ### Which version of floccus are you using? v5.4.5 ### How many bookmarks do you have, roughly? 1000000+ ### 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. ungoogled chromium 136.0.7103.113 ### 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 Access denied 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. [Bu hata hakkında daha fazla bilgi](https://developers.google.com/identity/protocols/oauth2/policies#secure-response-handling) floccus bookmark sync geliştiricilerinden biriyseniz [hata ayrıntılarını](https://accounts.google.com/) inceleyin. Hata 400: invalid_request ### Expected Behavior google won't allow access. ### To Reproduce create new profile choose google drive ### Debug log provided - [ ] I have provided a debug log file
kerem 2026-02-25 22:39:39 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@github-actions[bot] commented on GitHub (May 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:2908168680 --> @github-actions[bot] commented on GitHub (May 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 (May 31, 2025):

Hello @universish

ungoogled chromium 136.0.7103.113

Ungoogled chromium has a specific fictitious response URI for OAuth flows that Google does not approve. See https://github.com/floccusaddon/floccus/issues/847 The consequence is that syncing Ungoogled Chromium Bookmarks with Google Drive doesn't work with floccus. I'm sorry about this.

<!-- gh-comment-id:2925137317 --> @marcelklehr commented on GitHub (May 31, 2025): Hello @universish > ungoogled chromium 136.0.7103.113 Ungoogled chromium has a specific fictitious response URI for OAuth flows that Google does not approve. See https://github.com/floccusaddon/floccus/issues/847 The consequence is that syncing Ungoogled Chromium Bookmarks with Google Drive doesn't work with floccus. I'm sorry about this.
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#1313
No description provided.