1482355 - TB 60 + Lightning 6.2 loads intermittently Google calendar birthday records

Status: RESOLVED WORKSFORME

(Calendar :: Provider: CalDAV, defect)

Description

[Leopoldo Saggin]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180807170231

Steps to reproduce:

I installed TB 60.0 official released version over my previous version 52.9.2.
This way also the bundled Lightning component was updated.
I have 8 Google calendars I sync with Lightning by using CalDAV method.
In particular I have a "Birthday date Google Calendar" which contains 175 records, ie I have 175 persons out of about 420 of my Google contacts whose birthday date field is filled in.


Actual results:

The sync apparently is ok for all of the 7 others Google calendars.
This is NOT true for the "Birthday Google Calendar" which contains birthdays from my Google contacts.
In fact when I run TB60+Lightning I see that not all birthdays are loaded.
If I force a manual sync of the calendars inside TB+Lightning, then all the lacking birthdays are loaded.
BUT, if I perform a second manual sync, than those birthdays that were not present at startup, disappear again.
If I manually sync another time then they re-appear and so on.
It seems like a switch: they appear/disappear once yes and once no (=alternatively) Please note that:
a) Records that appear/disappear are always the same
b) It seems that there is neither an evident alphabetic nor birth date (older vs younger persons) relationship with records appearing/disappearing.
c) Maybe, but I'm not sure that records appearing/disappering could be those whose birth date I introduce more recently in the specification of the Google contact (but I cannot be absolutely ure about that).
d) This fact happens both if set the "birthday" calendar as read-write or read-only in TB60+Lightning.




Expected results:

Once all the birthdays are loaded in Lightning, they should not disappear anymore (this was the (correct) behaviour until TB 52.9.2+Lightning.

Regards,
Leopoldo Saggin aka Topoldo

Comment 1

[Leopoldo Saggin]

Another couple of info:
1. This behaviour is present both when the other 7 Google calendars are active and when they are disabled.
2. The oteh properties of the birthday calendar were set as default, ie:
   a. Offline support is set (checked)
   b. It can show alarms 

Regards,
Leopoldo Saggin aka Topoldo

Comment 2

[Wayne Mery (:wsmwk)]

(Note: you can file these directly in calendar product)

Comment 3

[[:MakeMyDay]]

Sounds like a caching issue. Can you please unsubscribe from that calendar to invalidate the cache, restart TB and subscribe again with offline support enabled, please? Please check the calendar on wehther the synncing is completed successfully. If so, please restart TB and check if your calendar is still complete or the issue occurs again.

Comment 4

[Leopoldo Saggin]

I tested what was suggested in comment #3

1. Can you please unsubscribe from that calendar to invalidate the cache, restart TB and subscribe again with offline support enabled, please?

Done.

2. Check the calendar on whether the syncing is completed successfully.
Done. It seems to show all data.

3. If so, please restart TB and check if your calendar is still complete or the issue occurs again.
The issue occurs again :-(

Comment 5

[Leopoldo Saggin]

Could be useful if I export my calendar to .ics and send it to you to test it?
As its private, I prefer not to attach here, of course.

Comment 6

[ravi125]

thanks for providing this kind of post.it's very useful post.
http://aktechnoservice.com/ifb-service-center-in-hyderabad/

Comment 7

[Stefan Sitter [:ssitter]]

Do you get any error messages in Tools > Developer Tools > Error Console when the problem occurs?

Comment 8

[Leopoldo Saggin]

@Stefan Sitter:
I did not checked Error Console when problem occurred.
Anyway, in these days I'm on vacation and I'm using another computer (where I also have TB60) which sync all the Google calendars I use also in the other PC. Apparently here I have NO problems. So it could be really a "local" (ie cache) problem.
As soon as I come back, on next week, I'll re-test the "original" where I suffered the problem and a third PC and then I'll update Bugzilla about this problem.
So, please wait for at least on next Tuesday 19 or Wednesday 20 to have some more news.    
Regards.

Comment 9

[Leopoldo Saggin]

Today I went back to the work and even on the work computer (which was that where I noticed the problem at first), it seems that everything is ok again. Now I must check my desktop at home and I will do tonight. If this PC is also ok, I can conclude that everything is ok and I can close the issue. Maybe it was really a cache problem which was not correct by te initial empty of the cache. Anyway I'll confirm the possible (or, better, probable) closure in a short time.

Regards,
Topoldo

Comment 10

[Wayne Mery (:wsmwk)]

per comment 9