Sparkle

Couldn't find an appropriate update in the downloaded package

Asked by Jon C. Munson II

Namaste!

Relative to the above issue, I have checked the following in the appcast:

1. Package name is the same as app name.
2. Spelling/case appears correct.

What else could cause that error?

Here is the relevant info from the appcast (with some edits, the url is correct):

<enclosure url="http://.../StashWizK.pkg.zip" sparkle:version="25" sparkle:shortVersionString="1.25" length="9229128" type="application/octet-stream" sparkle:dsaSignature="..." />

Is it possible the 12k+ errors I am getting on permissions/owner/group in the package are the culprit? (Anyone with solution to the permission/group/owner problem, feel free to chime in as I'm still trying to solve that one, that happened after I ran Disk Utility to fix the permission problems PackageMaker reported originally)

Thanks!

Peace, Love, and Light,

/s/ Jon C. Munson II

Question information

Language:
English Edit question
Status:
Solved
For:
Sparkle Edit question
Assignee:
No assignee Edit question
Solved by:
Jon C. Munson II
Solved:
Last query:
Last reply:
Revision history for this message
Andy Matuschak (andymatuschak) said : 		#1

Hm. Permissions are unlikely to be the culprit, unless you don't have read access to the .pkg.

Is the name of Sparkle's *host app* StashWizK.app? Is that its actual file name on disk?

Revision history for this message
Jon C. Munson II (jmunson-his) said : 		#2

Namaste!

Thank you for the reply.

Yes, the app name you've cited is correct.

Peace, Love, and Light,

/s/ Jon C. Munson II

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

Hrm. Please send me a copy of your app, the .pkg you're trying to use to upgrade, and a link to your appcast at <email address hidden>. I'll debug it as soon as I get a chance, but it may be a little bit.

If you want to speed things along, you should be able to discover the problem pretty trivially by compiling breaking in SUInstaller.m:42 and stepping through the loop that isn't finding your .pkg.

Revision history for this message
Jon C. Munson II (jmunson-his) said : 		#4

OK...

I had to rebuild the package to get the correct name in place. Simply changing file names didn't do it.

At any rate, all is well now!

Thanks!

Peace, Love, and Light,

/s/ Jon C. Munson II