mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #1921] Setting up Profile gives 'Access Blocked' when signing in to gmail #1285
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#1285
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @johnaaronrose on GitHub (Apr 22, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1921
Which version of floccus are you using?
5.3.4
How many bookmarks do you have, roughly?
Approx 40
Are you using other means to sync bookmarks in parallel to floccus?
Yes. Chromium on another PC and Floccus app on an Android tablet.
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.
Chromium 135.0.7049.84 (Official Build) snap (64-bit) under Ubuntu desktop Noble
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
Expected Behavior
Window asking for parameters of Floccus Profile.
To Reproduce
Create Floccus Profile. Supply gmail details. Complete Floccus Profile parameters.
Debug log provided
@github-actions[bot] commented on GitHub (Apr 22, 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 💙
@marcelklehr commented on GitHub (Apr 22, 2025):
Hey @johnaaronrose
Thanks for opening a complete issue report. Can you click on "error details" and make a screenshot of that too (removing sensitive data)?
@johnaaronrose commented on GitHub (Apr 22, 2025):
Clicking on Error Details gives this window:
@marcelklehr commented on GitHub (Apr 22, 2025):
Mmh, how did you install the extension? When installing from the chrome webstore, the redirect_uri for me is
https://fnaicdffflnofjppbagibeoednhnbjhg.chromiumapp.org@johnaaronrose commented on GitHub (Apr 22, 2025):
I dragged the crx file (floccus-build-v5.3.4) when installing as per I think the way I did it on the first PC. I don't know what the redirect_uri was or even if I saw it. How do I find out what it was?
@marcelklehr commented on GitHub (Apr 23, 2025):
Ah, I see, I can confirm that this is a correct redirect_uri for floccus and can reproduce the error when installing from the CRX file. I've tried to correct the Google OAuth settings to hopefully make this work. Can you try this again in a few hours from now?
@marcelklehr commented on GitHub (Apr 23, 2025):
Btw, is there any reason you're using an outdated version?
@johnaaronrose commented on GitHub (Apr 23, 2025):
Floccus now working OK on Chromium (in Ubuntu desktop Noble) after inputting gmail credentials again. The reason that I'm using crx version 5.3.4 (rather than latest 5.5.2) is that I did the crx 'install' in November 2024 on first computer and so I didn't think to use latest crx on second computer. Should I update both computers to 5.5.2 crx?
@marcelklehr commented on GitHub (Apr 23, 2025):
I recommend to update to the latest version, yes, if possible regularly, to benefit from the improvements and bug fixes I release, usually on a bi-weekly basis.
@marcelklehr commented on GitHub (Apr 23, 2025):
I'm glad it works now. I'm thus closing this.