App crashes after update with Sparkle framework

Discussion in 'Mac Programming' started by barenature, Nov 12, 2010.

  1. macrumors newbie

    Oct 11, 2010

    I use the Sparkle framework to deliver updates to the user of my application, but when I test it myself and click the familiar "Install and Relaunch" button, the app is installed, but crashes on relaunch.

    The crash report says the following:

    *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'launch path not accessible'
    I have done some googling and I think this is due to the fact that an application downloaded from the internet does not have the permission to execute, hence the familiar dialog that pops up when you first launch an application that has been downloaded from the web.

    I am a bit confused, though, because how does one go about and alter these permissions to allow the Sparkle to work properly? In other words, why does the application not have the "correct" permissions even though a previous version has been installed and launchd before?

    Any pointers or help is appreciated.

  2. thread starter macrumors newbie

    Oct 11, 2010
    It seemed to be a problem with the Sparkle framework itself. I downloaded and compiled the most recent version of the framework from GitHub and all works fine now. Odd.

    Any pointers or comments are still welcome as they might help in solving this bug.

  3. macrumors 604

    Aug 9, 2009
    The bug was solved in the latest Sparkle version.

    If you want to see the cause of that bug, do a diff between the Sparkle version that works and the version that fails. Also read the checkin notes or release notes to see if they say anything relevant.

    Otherwise it's all just guessing, which has a low effectiveness as a debugging strategy.
  4. thread starter macrumors newbie

    Oct 11, 2010
    It's only a bit confusing for the users that the "old" version is still downloadable on the Sprakle website (not GitHub), but I guess Andy (the creator of Sparkle) swamped with work at the moment.

    Anyway, I'm glad it's solved now and it's amazing that this framework is free to use by developers.

    Thanks for your input!


Share This Page