Running Sparkle updater complains about signatures

[wincent]

This is running 4.76beta, and trying to download 4.99beta.

[ben-willmore]

I can't find the old key that I used to sign Isolator. I will see if I can dig it out. But I'm surprised that automatic updates are working at all -- I thought that recent changes to OS X prevented the updater from contacting the server. Can you confirm what version of OS X you are using?

[wincent]

Running 10.11.4 (15E65).

[ghost]

Same behaviour here on OS X 10.11.4. Anyway, I just manually downloaded the latest 4.99b and copied it over the old one.

If you post a note here on the project main page, to download 4.99b so that future updates work correctly, it'll overcome this issue (I've seen other apps which change their update system to post that message in the Sparkle update window itself).

[mikaeleiman]

Same thing on 10.12.5, FYI.

[gamebits]

Perhaps related, while running Isolator 4.99b in macOS 10.13.6, Little Snitch reports an error when Isolator tries to connect to www.willmore.eu:

The code signature of the process has a formal error. This probably indicates that somebody is trying to pretend a valid code signature, or that the developer used inappropriate, non-standard tools to create the signature.