KPGoogleSybc no longer works.

[mpapini64]

Since this morning, this plugin has stopped working on all my PCs at the same time.
What tells me that the app is blocked after I enter my account email
I contacted Google support (I have Google One) and they told me that if Google has decided to block the app it is because it is violating its standards.
So this plugin is no longer in compliance with the standards?

To Reproduce

• I entered the email in the configurator
• the Google Sign-in form opened
• the browser window opened to choose which email to enter with.
• entered the email it tells me
  This application is blocked

Expected behavior
I expect it to ask me for my password and ask me for confirmation on my mobile phone and finally ask me to confirm that I can access my files.

Screenshots

Please provide the following information:

• Edizione Windows 11 Pro Versione 23H2 Data installazione: ‎19/‎01/‎2024 Build sistema operativo 22631.4460
  Esperienza Windows Feature Experience Pack 1000.22700.1047.0

• Chrome Versione 131.0.6778.70 (Build ufficiale) (a 64 bit)

• Plugin Version 4.1.0

• KeePass Version 2.57.1

• "Normal" KP installation

• 

[Unlifate]

I also have this issue, but this solution works as a workaround:
@liteCarma in #79 (comment)

[0belius]

Actually even this is enough

[mpapini64]

The solutions you (@Unlifate and @StephanFA) propose necessarily require the generation of the client and secret id, which I do not have, furthermore I doubt that I would solve this inconvenience, Google considers the app or rather the plugin not safe, at least that's what Google One support told me.
Anyway I found a valid replacement for this plugin, I made three triggers, the first that synchronizes the current DB with a synchronized copy on the Cloud, when a save is made, the second that synchronizes when the DB is opened and finally a third that adds a button and allows you to synchronize manually.
In this way I replaced all the plugin's features.
Obviously on the mobile, my KeePass points to the DB on the cloud directly, since the app does not have the triggers engine.
Anyway if the developer provides me with a solution, then welcome.

[generalmimon]

@mpapini64:

The solutions you (@Unlifate and @StephanFA) propose necessarily require the generation of the client and secret id, which I do not have,

No, you're mistaken, #79 (comment) suggested by @StephanFA does not. Look at the screenshot in #79 (comment) carefully - the Client ID and Client Secret input fields are disabled (grayed out), so you don't have to and in fact can't enter anything there. Apparently, they are disabled as long as you leave the Use KeePass Google Sync 3.0 App Credentials checkbox checked.

The workaround in #79 (comment) works for me and is very easy to do - I literally just ticked two checkboxes and everything works like clockwork again.

[wenz]

I can confirm what @generalmimon wrote in #83 (comment). Works like a charm (at least for now)!

[golf247]

I tried #79 but it did not work for me. It still wanted new credentials. My work around for the time being was to install drive for desktop and setup Triggers for OnOpen and OnSave to sync to the local G drive version. Not as nice as KPSYNC and would require G drive on every PC. Some PCs had a limited access DB that still sync'd to my Gdrive using KPSYNC, thus hoping there is a way to fix this.

Walter I will say thank you for past and any future efforts. I suspect google is getting tougher to stay logged in with 'key' type of credentials, vs having to 2FA every time.

[Robopwner]

I had this issue as well.
I somehow had the Legacy OAuth2.0 ID & Secret, and once those were cleared and use KeePass Google Sync 3.0 App Credentials and Use Limited Driver Access checked, I was able to sign-in and use KPSync again.
This issue should be looked into.

[sudeshchouhan]

Thanks a lot @generalmimon, it works.

[dregad]

Duplicate of #79