Sparkle

Update filename cannot be long?

Asked by SnowClic

I managed to get Sparkle working for my bundle, and it is great. However, I found a strange behavior depending on the... length of the update filename? Here is the situation.

I have a pair of bundles (a quicklook anda prefpane) which are called Foo.qlgenerator and Foo.prefPane. I am trying to use Sparkle for the first time with the version 2.2.0 of this bundle pair. The update is made of a .pkg that contains both bundles. What is strange is that if I call my update Foo.pkg.zip, it works. If I call it Foo2.2.0_2009-12-22T17.00.pkg.zip it doesn't. If it is less complicated like Foo220_2009-12-22T17-00.pkg.zip (i.e. with less dots), doesn't work either.

The error is that the update is improperly signed. But I have used the exact same steps to produce the two packages (and I sign the .pkg.zip not the .pkg) The two are in the same directory on my server. I just change the filenames and dsaSignature in the appcast. And the long one isn't just renamed in the Finder or the Terminal but truly created with PackageMaker. A I doing something stupid?

Question information

Language:
English Edit question
Status:
Answered
For:
Sparkle Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Andy Matuschak (andymatuschak) said : 		#1

Huh! Anything interesting in the console?

And, a hunch: what if you remove the underscore in the filename but keep it long?

Revision history for this message
SnowClic (k-postmaster-softtenebraslux-com) said : 		#2

Hi Andy.

No nothing interesting in the console. I tried without the underscore (replaced with a minus sign). Doesn't work either. I got a "Couldn't find an appropriate update in the downloaded package." error. I tried again with my short filename Foo.pkg.zip to make sure I wasn't doing something wrong, but definitely, the short name works well, and the Installer is launched.

Very strange. I keep investigating.

Revision history for this message
Andy Matuschak (andymatuschak) said : 		#3

Aha! Your package must have the same name as your app (that is the cause of the error message quoted). Nominally, your .zip should not have to also, but perhaps that's seeped through.

Revision history for this message
SnowClic (k-postmaster-softtenebraslux-com) said : 		#4

Dear Andy,

I am glad you understood the sense of the error message. However, isn't strange that my package must be called with the same name as my app? It isn't a feature, to me. Fortunately, both my quicklook and preference pane have the same name Foo.qlgenerator and Foo.prefPane. But what if the two had slightly different names?

I can live with this behavior, but it is a limitation to me. If you can manage to do something about it, I would be glad.

Thanks for your support.

Revision history for this message
Andy Matuschak (andymatuschak) said : 		#5

Yeah, I see how this is totally unintuitive.

This requirement is because many people ship distributions with one "Install" pkg and one "Uninstall" pkg. This was a simple, though perhaps not extremely elegant, way to determine uniquely which package in the distribution was the correct one to install.

It uses the name of the bundle provided to updaterForBundle, so it'd be okay if your files had distinct names.

Can you help with this problem?

Provide an answer of your own, or ask SnowClic for more information if necessary.

To post a message you must log in.