Changed App name won't update?

[zsszatmari]

Dear All,

I have a problem. I have an app, call itt Awesome.app. rename it 'Awesome update test.app'. Then I'd like to release a new version with different name 'Awe-some.app'. I zip it, update the updater xml, and get

Sparkle Error (continued): Couldn't find an appropriate update in the downloaded package.

I don't really need it to be renamed for old users, but I'd like to see the update to work...
If I rename the same new version bundle to Awesome.app, and zip it, the update works flawlessly.

So my question is, how do I have an 'appropriate update' in the downloaded package? I read that Sparkle can find the .app by bundle id (in the Info.plist), but it does not seem to be true, am I missing something?
Thank You for your help!

I am on Sparkle 1.5b6

[kainjow]

Glancing at the 1.5b6 source code, it looks like it accepts a package (.pkg or .mpkg) if the package's name matches the bundle name. So you could try bundling your new app in a package installer, place that in the zip with the old app name and have the installer replace the old app with the new app.

[kainjow]

Related issues #62 and #264.

[gnachman]

I have a hacky solution to this at https://github.com/gnachman/Sparkle, commit gnachman@bd6a8df.

To use it, set SUFeedAlternateAppNameKey in the user defaults to the name of an alternate app name to accept as the root folder int he zip. My plan to roll this out is:

1. Everyone is running MyApp
2. Begin distributing MyApp with SUFeedAlternateAppNameKey=MyNewApp. The CFBundleExecutable and CFBundleName can change as long as the folder (MyApp.app) remains the same so older clients can still update to it.
3. Eventually, 9x% of users will have installs with SUFeedAlternateAppNameKey set. Then I can change MyApp.app to MyNewApp.app in the zip file I publish.

[kornelski]

Does #469 help here?

[zorgiepoo]

Tracking better app rename changes with #62 (although it's more for app bundles, not pkgs..)