Cookie 3.3 is not updating itself on 10.7.5



  • My software installation log shows I allowed Cookie 3.2.3 to update itself to 3.3 on October 21. That update worked fine.

    On November 7, Cookie offered to update to 3.3.1, which I allowed. And again on November 9, it offered to update to 3.3.2, which I allowed.

    A short while ago, Cookie again offered to update to 3.3.2. When I checked my log, it showed I'd already updated … but it never happened. I'm still running Cookie 3.3.

    I carefully watched this repeat of the 3.3.2 update. After clicking the "Install" button, the update downloads. When the download finishes, the update window disappears, and the Cookie icon disappears from the menu bar. That's it – the app doesn't get updated, and Cookie does not relaunch.

    I'm holding off on manually downloading the latest release and installing it to give time for comments and suggestions.

    -- Ward



  • I'm out right now,
    But I'll check my update manifest when I get home.
    Thanks for the heads up.



  • Hmmm,

    I just tested on Yosemite and all is ok.
    This must have something to do with the fact it's now built on xcode6.1?

    I'll see what I can do.



  • Russell, I send a tweet on this issue a week ago but never got a response.

    I have the same problem on a Machine with 10.8.5 with 3.3. It showed both the 3.3.1 and 3.3.2 Sparkle updates after download Cookie gave a crasher. I solved the issue by manually downloading Cookie 3.3.1 and 3.3.2 and drop it on the Application folder.

    Machine with 10.0 is fine with Sparkle updates ! 🙂



  • Xcode6 must have broken Sparkle?
    I'll see if any other devs have the same issue, and if there is a workaround



  • I fired up a virtual machine, and see this happening on 10.7, and 10.8, (i don't currently have10.9 to test with) 10.6 seems to work ok.

    I have recently changed the way I code sign the Sparkle updater, ill roll back to the old method, and see if that fixes the issue.

    if it does.... unfortunately this means, that everyone (on 10.7, 10.8, and possibly 10.9) will have to do a manual update to v3.3.3 when it comes out....

    maybe it was dumb luck, as it would have minimised the number of people updating to 3.3.1, which had the Firefox bug in it...

    sorry for the inconvenience folks.
    Its not the easiest supporting 5 different OS's

    🙂



  • ok so I have this fixed, and have uploaded a newer version of 3.3.2 to my site.
    This should fix any future updating issues.
    I would recommend manually updating to v3.3.2, for those who are having updating issues.

    I tested it on 10.6, 10.7,10.8,10.10 and it updated on all OS's.

    for anyone who's interested, I updated from Sparkle 1.5b6, to Sparkle 1.6.1.
    I would have preferred the latest 1.8 version, but that is incompatible with OS X 10.6.

    anyway,
    I have a few bugs i need to fix for v3.3.3, so ill get to work on that now.



  • 3.3.2 to 3.3.3 Sparkle update fails after download giving crashers.

    EDIT: solved issue by installing 3.3.2 version from November 12th and then applying Sparkle update to 3.3.3.



  • 3.3.2 to 3.3.3 Sparkle update fails after download giving crashers.

    EDIT: solved issue by installing 3.3.2 version from November 12th and then applying Sparkle update to 3.3.3.

    Perfect.
    I did do a silent update on v3.3.2 with the updated Sparkle build.



  • I tested it on 10.6, 10.7,10.8,10.10 and it updated on all OS's.

    for anyone who's interested, I updated from Sparkle 1.5b6, to Sparkle 1.6.1.
    I would have preferred the latest 1.8 version, but that is incompatible with OS X 10.6.

    Probably best to drop Snow Leopard. It is no longer supported by Apple and has dozens and dozens of unpatched security vulnerabilities.



  • I know!
    but its not too much hassle to still support it....

    If I was going to drop 10.6, I would also drop 10.7 support. but while its still easy, ill keep them all supported.

    🙂