Note that there is no need for extra scopes. The default scopes should be sufficient.
The error you mentioned is caused by recent changes in the Google APIs.
The issue has been fixed in the latest version of TMS VCL Cloud Pack.
Please make sure you have correctly installed the latest version.
Thanks for your reply.
I have installed TMS VCL Cloud Pack 18.104.22.168 and my test cases pass again. Thanks for the update!
Mind you I have a tool for new customers to grant access to the calendar and create the Tokens string required for the INI file. In that tool I ask for the list of calendars belonging to the Google account my user has and let them select a calendar. This CalendarID is stored together with the Tokens in the INI file of my application server.
If I do this now as if I were a new user of my software I need to login to my Google account and it says "This app isn't verified". I select "Advanced" and can then click on the link "Go to Maranatha Consulting CRM Google-Calendar-Integration (unsafe)". Then I can allow access to my calendars and the reply from your HTTP server inside the TAdvGCalendar conmponent is "Application succesfully authorized. You can close this browser window". In the TCloudGoogleWin.DoCommandGet I can see that I get an access_token & refresh_token back from the Google API.
What has changed is that the TAdvGCalendar.DoAuth is no longer synchronous and I had to move the code to populate my calendar selection combobox into the event handler TAdvGCalendar.OnReceivedAccessToken. So it is all working again.
Form your experience how long will it take for Google to declare the application as safe & verified?
it seems the security tokens that my customers used to use on their app server are no longer working. So I have to ask them to login to their Google account and select the correct calendar again. Then the selected CalendarID and Tokens need to be updated in the INI file of their app server.
Could that be a side-effect of using the new Google Calendar API?
There haven't been any changes to the behaviour of the DoAuth call, but it is indeed recommended to use it in combination with the OnReceivedAccessToken event.
Please note that you'll have to manually request your Google App to be verified by Google. Unfortunately I'm unable to provide a timeframe to get your app verified as we have no control over this process.
It is possible that if you changed the settings in your Google App that existing tokens become invalid.