Google Spreadsheet Save Authentication Failed

Hi,
when I try to save a form in a Google Spreadsheet I have this error:

    [6] => Array
        (
            [Google Spreadsheet Save] => Array
                (
                    [Authentication] => Failed
                )

        )

In you guide I read:

If it doesn't work and you get an Authentication failed error in the debugger, then please check your username/password, if you are sure they are correct then you will need to create an app sepcific password for Google drive and use it instead.

How can I create an app sepcific password for Google drive?

Thank you!

Hello ajeje,
I'm not a Chrono professional, but after checking your new post, I think that the following links may help:
How do I use the Google Spreadsheet Save action?
P.S: I'm just an automated service😉

Hi ajeje,

Please check this Google FAQ

Bob

Hi Bob,
thank you for your quickly reply!
I have resolved the failed authentication through this link: https://www.google.com/settings/security/lesssecureapps

I followed your guide step by step however when I submit the form I have this error:

[AddResult] => Blank rows cannot be written; use delete instead.

I don't want to take advantage of your kindness, but if you want check my form I have attached (I have changed email and password) I will be very grateful!

P.S.
I advise you to add the file to the demos

Hi ajeje,

It works OK when I test. The values are saved and updated with no problems.

Bob

Hi Bob,
yes it works correctly, I was wrong to fill the fields of google spreadsheet 🙄

I noticed that if I save the data also in my database it save only the creation date, why?

Your db table fields names match the form fields names ?

Regards,
Max

Hi ajeje,

The saving problem may well be because the data is in the GSheet sub-array for the Google export. You'd need to add this as the Model ID in the DB Save action too.

Bob

Hello,

I am having the same issue. But my problem is only the authentication. Form Debugging shows [Authentication] => Failed
I have tried with two accounts one from Google Apps and one personal account. I also tried with and without two step authtentication enabled in the account.

I also tried to create an app password in my Google account. And used that password instead of the account's password in chronoforms. Dint work...

My form had been working for some time and yesterday it simply stopped working (there was no changes in my site)

I have tried so many things. Any hep is appreciated.

Thanks

Hi pabloapico,

I think I found the answer here
That said, the issue is most likely related to the use of ClientLogin for auth (username/password.) That was deprecated 3+ years ago and was just shut down for real. Migrating to OAuth2 should restore functionality.

It will need an updated action using OAuth2 to fix this I'm afraid. I don't know how easy that will be to fix, I'll let Max know.

Bob

Hi,

I'm having the same problem to authenticate, do you know if the the developers fixed the OAuth issue?

Thank you.

Gonzalo.

Hi Gonzalo,

Not as far as I have heard - Max has been very quiet recently so he may be working on it.

Bob

Hi Bob & Max,

Anxiously awaiting a patch...any ideas on if/when it's coming?

Thank you!

Guys this is a serious issue because website is running in a production environment and relies heavily on data save to Google spreadsheet.

Google just went and broke a lot of production websites with this latest change.

Hi,

After a lot of frustration, head-scratching and reading documents that don't make any sense to me - I have just managed to write a record from a ChronoForm to a Google Sheet using OAuth2.0 I don't have a usable action yes but this is an important step in that direction.

Bob

Hi,

I've now got to the point where I have a Google Sheet save working from an action. Still some rough edges to work on though.

If anyone reads this and is prepared to test an alpha maybe beta version please PM me.

Bob

Hi,

I think this is now working - please PM me if you can beta test.

Bob

Can't make Google Spreadsheet and ChronoForms working together. The authentification fails.
Did anyone succeed lately?