Node-red-node-google authentication isdues

[rowleya]

Which node are you reporting an issue on?

Node-red-node-google

What are the steps to reproduce?

1. Add calendar node
2. Add credentials and enter client id and secret
3. Authenticate with google
4. Deploy flow
5. Wait for token refresh to fail
6. Open calendar node
7. Open google credentials node but change nothing at all
8. Authenticate with google

What happens?

Authentication fails with invalid client id. If I re-enter client id and secret it works, so guessing it isn't saved.

What do you expect to happen?

1. Ideally refresh wouldn't fail. If it were possible to make refresh happen at half the refresh time instead of using the exponential backoff, this might work better? Or else having some manual config for refresh, like node-red-alexa2.
2. If refresh is going to fail often enough, reauth shouldn't require that I have to reenter my client id and secret.

Please tell us about your environment:

• [ x] Node-RED version: 1.2.9
• [ x] node.js version: 12.21.0
• [x ] npm version: 6.14.11
• [ x] Platform/OS: Server: Raspberry Pi 4 / Ubuntu Server 20.04, Client: Windows 10
• [ x] Browser: Chrome

[ratatine]

I'm running into the same issue. 0.2.0 with node-red 2.0.5. Node.js 14.17.4.

[rowleya]

I ended up using node-red-contrib-ical-events and then using the ical version of the calendar.

[ratatine]

I appreciate the feedback. I'm also using this to create events so I'd really like to see a solution if someone finds time to look into it.