floccus
floccus copied to clipboard
Google drive authentication
Which version of floccus are you using?
5.0.10
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
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
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. Preberite več o tej napaki. Če ste razvijalec storitve floccus bookmark sync, si oglejte podrobnosti o napaki. Napaka 400: invalid_request
Expected Behavior
authenticate to google drive for bookmark save
To Reproduce
new profile - google drive
Debug log provided
- [ ] I have provided a debug log file
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:
I cannot reproduce this, sorry. Can you try again, do you have other details that I could try to reproduce?
On Chromium Version 124.0.6367.220 (Official Build, ungoogled-chromium) (64-bit)
Error Details:
Request details: redirect_uri=https://fnaicdffflnofjppbagibeoednhnbjhg.ch40m1umapp.qjz9zk/
I had the same problem on ungoogled chromium. I managed to sign in eventually by exporting my floccus profile from a working browser and then importing it on chromium, as described here https://github.com/floccusaddon/floccus/issues/1267#issuecomment-1279057367 I'm still having problems to sync, but that might be unrelated.
Sometimes Google refuses to sign people in using floccus, but I don't know why, I haven't been able to reproduce this so far.
I'm experiencing the same error
Sometimes Google refuses to sign people in using floccus, but I don't know why, I haven't been able to reproduce this so far.
It might be related to using a VPN that google considers a potential bot address and requires extra login steps (captcha).
happening to me too with floccus app v5.2.5 on samsung S23 running android 14 (and chrome browser).
after I select the google account to be used and I confirm to continue the app returns to previous page (login with google) without showing any error (please consider adding at least an error message).
I have also tried importing a profile from browser, and at first it seems to be good, but on sync I get this error: E018: couldn't authenticate with the server.
the log is useless:
2024-08-23T09:34:04.390Z Starting sync process for account mio 2024-08-23T09:34:04.397Z onSyncStart: begin 2024-08-23T09:34:04.472Z onSyncFail 2024-08-23T09:34:04.473Z Syncing failed with E018: Couldn't authenticate with the server. 2024-08-23T09:34:04.479Z onSyncFail
please consider adding at least an error message
I'll see if I Google provides a more detailed error message on what exactly is failing
In the meantime, I checked the Google API console: The error rate for floccus is currently hovering at around 0.1% from 60000 requests per hour, so this is not a very widespread phenomenon, I would say. Perhaps this is a form of censorship? May I ask which countries you reside in?
Same country as you.
huh
On Ungoogled Chromium this issue is expected as Google does not recognize the redirect URL that they use ( :see_no_evil: )
In the latest release the exact error should be logged
Can you please post a log of an unsuccessful sync attempt here?