(In reply to Stephan Richter from comment #3) > User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0 > > The original problem with the description of recurring events with no end (infinity) occured with the TB version update from 68.x to 78.x. In order to avoid backward compatibility problems I created new recurring events and performed modification activities like changing the description. > > Steps to reproduce and (interim) outcomes: > 1. the following steps are performed directly in the TB calender (in contrary to directly on the calender on a mobile device) > 2. assure during reproduction that you UPDATE and only READ the mobile calender. > 3. Please see my corresponding comment at the end! > 4. CREATE NEW recurring event e.g. bi-weekly with no end date on Wednesday, starting on 3rd of February 2021 and wait until event is updated on the server and visible on the mobile device > 5. ADD individual description to a spezific event of recurring event (e.g. "hello world first" on 3rd of February 2021) > 6. SAVE changes to spezific event and check results in TB and on mobile device > > Interim outcome: > In TB and mobile device > Expected outcome: individual description "hello world" appears in spezific calender event on 20th of February > Actual outcome MEETS expected outcome > > 7. PRESS 'SYNCHRONIZE' button in TB calender > > Interim outcome: > In TB and mobile device > Expected outcome: individual description "hello world" appears in spezific calender event on 20th of February > Actual outcome MEETS expected outcome > > 8. ADD individual description to a spezific event of recurring event (e.g. "hello world second" on 20th of February 2021) > 9. SAVE changes to spezific event and check results in TB and on mobile device > > Interim outcome: > In TB and mobile device > Expected outcome: individual description "hello world second" appears in spezific calender event on 20th of February > Actual outcome MEETS expected outcome > > 10. PRESS 'SYNCHRONIZE' button in TB calender and check TB and on mobile device > > ****************************** > Outcome (BUG identification): > In TB > Expected outcome: individual description "hello world second" DOESN'T appear in spezific calender event on 20th of February > Actual outcome DEVIATES from expected outcome in the way that it isn't displayed anymore > > In mobile device > Expected outcome: individual description "hello world second" appears in spezific calender event on 20th of February > Actual outcome MEETS expected outcome > > Conclusion: Changes (SAVING after ADDING descriptions) are successfully transferred to the server. After the synchronizing action the content of the description isn't displayed in thunderbird anymore, however the change is correct and available on the server and also correctly displayed on the mobile device. > ****************************** > > @ step 3. DON'T perform any changes to events on the mobile device. If you do so it becomes really messy up to dataloss! I didn't go into that issue yet. > > Best, > Stephan Hello Stephan. Thank you for the detailed analysis! I don't understand it however. Are these steps to reproduce this bug or are you also reffering to lo
Bug 1684359 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I was able to reproduce this after some fiddling but it seems like the synchronization takes place if you restart Thunderbird.