JSCalendarSync v0.24 released


This new version should fix the dreadful “Can not start sync session” that some users have reported to appear when first starting the application, making it unusable for them.

Should you have encounter this error with previous versions I encourage you to download and test this new version, and report any problem you might find.

If everything is working correctly for you, there is no need to upgrade, there is no other change made.

Why did I wait 6 months to correct this problem ? Actually, although several users reported this to me, I never managed to identify the problem from the log files I received. And I was not able to reproduce the problem on any machine I have access to (mine, my colleagues or my parents). However, since a couple of days, I have the pleasure to use a brand new Mac Book Pro. Today, I decided to start JSCalendarSync for the first time … and I received the error “Can not start sync session !”. I finally had access to a machine where the problem occurs, great. Debugging it was a matter of one hour only (mostly because I have not been browsing the source code since months), a very small error in the way I used to handle default values for the preferences file.

On the other hand : I have absolutly no clue why this problem appeared for some users only. Let’s hope this is now solved and that all users will be able to test and use JSCalendarSync.

  1. #1 by Jan Hendrik Mangold on 11/10/2006 - 11:54

    Sebastien
    on a Mac Pro I get this in my JSCalendar.log and my translate.crash.log is filling up rather quickly. Do you know what this is about?
    2006-10-11 11:40:43.070 JSCalendarSync[21025] *** Assertion failure in -[WCAPConnection fetchXMLFromURL:reportedError:], /Users/sst/projects/Cocoa/jscalendarsync/src/WCAP/WCAPConnection.m:97
    2006-10-11 11:40:43.071 JSCalendarSync[21025] fetchXMLFromURL can not work with nil URL

  2. #2 by Sebastien Stormacq on 11/10/2006 - 12:34

    Hello,
    I would suggest you to contact me in private to further debug this.
    At least it shows that my assertion are doing their job, without this, you surely have had a crash with core dumped 🙂
    Seb

(will not be published)