Rated 4 out of 5 stars

(see my two previous comments)

Now I think I know what happened.

The day I switched to version 1.0.x (some day in November '14), the add-on suddenly turned ALL PRESENT AND FUTURE EVENTS to status "Tentative", leaving PAST EVENTS untouched.

But once this has been carried out, new events could be created normally, with the correct "Confirmed" status.

The only cure was lengthy manual reset...

I hope it won't happen again!

This review is for a previous version of the add-on (1.0.3). 

Rated 4 out of 5 stars

@Philipp Kewisch, see initial post below

Yes, I am using an Android Phone, even two... But everything went smoothely until the switch 0.3.2 => 1.0.x

And everything looks fine on my phone(s).

Not sure I am able to enter a technical debug session, but I'll take a look.
Meanwhile, maybe you get a solution on your side.

Thanks for support anyway!
NL

This review is for a previous version of the add-on (1.0.3). 

Rated 4 out of 5 stars

First of all, thank you very much for providing this addon!
Now fully part of the Firefox/Thunderbird/Google ecosystem.

Used to work mostly fine through all these years, with a recent glitch in the latest version.

My test case: TB 31.3.0 FR / Lihting 3.3.1 / GA Provider 1.0.3 / Win7 Pro FR

With this versions ALL EVENTS ARE MARKED AS "TENTATIVE" (in French: "Provisoire"), thereby appearing greyed in calendar.

Of course one can edit each event and manually set status to "Confirmed" (in French: "Confirmé"), BUT THIS IS NO SOLUTION.

Tried to uninstall/reinstall GA Provider, tried previous versions, tried restarting TB, nothing worked...

Seems like a bug in GA Provider.
In this case, when do you plan a fix?

If not a bug, is there a way to mass-edit events and set ALL statuses to "Confirmed"?

Thank you in advance
NL

This review is for a previous version of the add-on (1.0.3). 

I've heard of this before and last time it was an issue with the Android calendar marking events as tentative. Are you using an Android phone? There is no way to mass-edit items unfortunately. I'm surprised though it wasn't already happening before, I didn't change much in the code to detect the status from 0.32. Could you visit the support forum and show me some logs from when events are created and synchronized? You will find out how to enable debugging in the FAQ.