I'm not sure this is possible using only the vanilla Sparkle framework. The reasoning is that the file name of the application can differ from the CFBundleName
defined in Info.plist. Sparkle needs to ensure it is updating the correct file system structure, no matter what it may be named.
Consider the following scenario:
- User downloads and installs
Adium.app
whose CFBundleName
is Adium
.
- User renames it to
Instant Messenger.app
.
- Sparkle downloads and installs an update.
- After the update, the file name of the newly updated app is still
Instant Messenger.app
and the CFBundleName is still Adium
.
You can either hope that the fact that your application name has changed in the menu bar will prompt the user to rename it themselves, or your can pull some trickery at application startup to quit the application, rename it, and re-launch it if certain criteria are satisfied. I don't recommend the latter though, users do not like applications deciding to move themselves around without permission.