Google calendar entries not created

[Oliver]

Dear Team,
using the version from Dean from 2016-03-02 will not throw exceptions on todo items
https://sourceforge.net/p/lngooglecalsync/discussion/943517/thread/ce31efd2/7df9/attachment/lngsync.jar
but does not create anymore calendar entries.

WHat is the reson for that?

Automatic sync-on-startup is enabled. Starting sync - 4/20/16 11:12:11 AM
Application Version: 2.8 Beta 5
OS: Windows 7 6.1 build 7601 Service Pack 1 x86
Java: 1.6.0 IBM Corporation
Java Home: C:\Program Files (x86)\IBM\Lotus\Notes\jvm
Java Classpath: C:\Program Files (x86)\IBM\Lotus\Notes\jvm\lib\ext\Notes.jar;E:\install_files\LotusNotesGoogleCalSync\LNGoogleCalSync_2.8beta\lngsync.jar
Java Library Path: C:\Program Files (x86)\IBM\Lotus\Notes\jvm\bin;.;C:\Program Files (x86)\IBM\Lotus\Notes\;C:\Program Files (x86)\IBM\Lotus\Notes\Data;C:\Program Files (x86)\CA\SC\CAWIN\;
Local Server: true
Destination Calendar: Lotus Notes
Local Date Format: M/d/yy
Server Date Format: Detect
Use Proxy: true
Use Proxy Username: true
Sync On Startup: true
Sync All Subjects To Value: false
Sync Location and Room: true
Sync Description: true
Sync Alarms: false
Sync Days In Past: 5
Sync Days In Future: 21
Date range: 4/15/16 thru 5/11/16 (-5 to +21 days)
Getting Lotus Notes calendar entries
Using Detected Server Date Format: dd-MM-yyyy
Calendar query: SELECT (!@IsAvailable($Conflict) & @IsAvailable(CalendarDateTime) & (@Explode(CalendarDateTime) *= @Explode(@TextToTime("15-04-2016 - 11-05-2016"))))
Number of query results: 24
Couldn't determine end date; using start date. Subject: Extended Management Team Meeting - To Do and MoM
Getting Lotus Notes calendar entries (done in 5.8 s)
40 Lotus entries found within date range
Lotus Version: Release 8.5.2FP2|March 23, 2011
Logging into Google
Found Client ID file: E:\install_files\LotusNotesGoogleCalSync\LNGoogleCalSync_2.8beta\client_secret.json
Logging into Google (done in 0.0 s)
Finished sync (5.9 s total) - 4/20/16 11:12:17 AM

[Oliver]

seems that the Beta 2.8 version doesn't show when the client secret has a problem.

Solution: Use 2.7 client version!