Improperly signed update

Actually, your app verifies and updates correctly for me, also explicitly verifying the signature goves no problem. So probably something else goes wrong, perhaps it's your test setup that does not work. So what actually fails?

The only error message I get is at the end of the install, the
"improperly unsigned update" message dialog that pops up.
Unfortunately I've received support email from customers saying that
auto-update didn't work for them, so the problem exists beyond my
setup. At one point I did check and it did seem to work - that's why I
released it in the first place.

If you have verified the signing and it's ok, is there anything that
could bring up the "improperly unsigned" dialog as well?

I am not sure if the previous version of my app is using another
version of Sparkle, and that could be a problem. In any case, we are
talking about a few months only - not years or anything like that.

Thanks for looking into this. I appreciate your help.

On Jul 30, 2009, at 7:08 PM, Hofman wrote:

> Your question #78600 on Sparkle changed:
> https://answers.launchpad.net/sparkle/+question/78600
>
> Status: Open => Needs information
>
> Hofman requested for more information:
> Actually, your app verifies and updates correctly for me, also
> explicitly verifying the signature goves no problem. So probably
> something else goes wrong, perhaps it's your test setup that does not
> work. So what actually fails?
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/sparkle/+question/78600
>
> You received this question notification because you are a direct
> subscriber of the question.

Are you sure the older app has the correct (same) public key? That's the only thing I can think of. Have you actually tested with the old app version (the same that reports problems)?

Maybe that's what the problem is. The older app doesn't have a key. We
weren't using signatures before but are now. It looks like we don't
have choice with the new Sparkle release, correct?

-et

On Jul 31, 2009, at 10:48 AM, Hofman wrote:

> Your question #78600 on Sparkle changed:
> https://answers.launchpad.net/sparkle/+question/78600
>
> Status: Open => Answered
>
> Hofman proposed the following answer:
> Are you sure the older app has the correct (same) public key? That's
> the
> only thing I can think of. Have you actually tested with the old app
> version (the same that reports problems)?
>
> --
> If this answers your question, please go to the following page to
> let us
> know that it is solved:
> https://answers.launchpad.net/sparkle/+question/78600/+confirm?answer_id=2
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/sparkle/+question/78600
>
> You received this question notification because you are a direct
> subscriber of the question.

That's right. Okay, so don't sign the first update with 1.5b6, but make sure that version has the public key in it. Then sign all subsequent updates.

Great. Mistery solved. I appreciate your help. Thanks!

-et

On Aug 3, 2009, at 5:33 PM, Andy Matuschak wrote:

> Your question #78600 on Sparkle changed:
> https://answers.edge.launchpad.net/sparkle/+question/78600
>
> Status: Open => Answered
>
> Andy Matuschak proposed the following answer:
> That's right. Okay, so don't sign the first update with 1.5b6, but
> make
> sure that version has the public key in it. Then sign all subsequent
> updates.
>
> --
> If this answers your question, please go to the following page to
> let us
> know that it is solved:
> https://answers.edge.launchpad.net/sparkle/+question/78600/+confirm?answer_id=4
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.edge.launchpad.net/sparkle/+question/78600
>
> You received this question notification because you are a direct
> subscriber of the question.

That's correct. If the old version does not have a key, but it's using 1.5b6, it won't be able to update. Unfortunately there's no workaround, because your users already have the broken app. Perhaps the best thing to do is to mention something to this effect in your release notes linked or included in your appcast, and possibly link to a manual download page.