Helmo,

Thank you for posting that snippet from your Console log on MacUpdate.  Here is the important part…

Library not loaded: @executable_path/../Frameworks/Sparkle.framework/Versions/A/Sparkle
Referenced from: /Users/helmo/Downloads/BookMacster 1.14.10/BookMacster.app
/Contents/Frameworks/Bkmxwork.framework/Versions/A/Bkmxwork

Unfortunately, I have to get really technical here.  The problem is that "@executable_path/.." near the beginning.

But the problem on top of that is that, although @executable_path/..… is the default install path for frameworks in Mac OS X, we applied a script to our framework after building which tweaked it, changing that part to @loader_path/.   To make a long story short, it must be @loader_path/ or else BookMacster will fail to launch as it did for you.  I think you may need Apple's Developer Tools installed on your computer for the following to work, but the log you posted on MacUpdate also indicates that you probably have those, so if you could please check it out…

To be 100% sure, I just downloaded BookMacster from our site to verify that this is what we shipped.  It identifies itself as BookMacster version 1.14.10.  Cool.  I installed it in my /Applications folder, then ran this command in my Terminal…

otool -L Bkmxwork | grep Sparkle

and I got the following answer

@loader_path/Frameworks/Sparkle.framework/Versions/A/Sparkle (compatibility version 1.5.0, current version 1.5.0)

which is exactly what I expect, what BookMacster needs, and it should work.

The first few words are the part which is in dispute.  Possibly, yours will start with @executable_path/.. instead of @loader_path, and in that case indeed BookMacster would not launch.

Either way, this is mind boggling.  Let me know what you find, and/or please zip and send us the BookMacster 1.14.10 which you have that won't launch, so I can check it out myself.  It's 15 MB, so you should use a service such as sendspace.com.

Also, we need to sleep on this, because I'm out of ideas right now.  We've tested this on three Macs here and it works fine for us.

Thank you!

Is anyone else having this problem?