Maccy can't be updated from 0.9 to 0.10

[MaxDesiatov]

After I select "Check for updates" menu item and wait for the update download to complete, I always get this error:

This is stably reproducible for me on macOS 10.15.5 (19F101)

[p0deje]

Hm, can't reproduce locally. Can you try downloading from Github and running? Maybe that will give an insight.

[MaxDesiatov]

I've downloaded 0.10 from GitHub, but then after launching it from that archive I get this error:

I know I can disable Gatekeeper or give an exemption to this single binary, but I'm not going to do that for obvious security reasons. I wish Maccy binaries were notarised for macOS.

[p0deje]

Maccy 0.9 is not notarized as well, so I don't follow why you are fine running 0.9 but not 0.10. I believe that might be a cause of update problems. Feel free to stick to 0.9 if you don't want to exempt 0.10.

I currently work on 0.11 which will also be notarized (see #52 for more information).

[MaxDesiatov]

Sorry about the confusion, now I remember that I've built 0.9 from sources to sign it with my own cert. Rebuilding 0.10 now 🙂

I'd like to join the rest of the people in #52: I appreciate your hard work and would definitely buy Maccy on the Mac App Store when it's available there 👍

[p0deje]

Oh, that makes total sense. The good news is that I've already made notarization work so hopefully, nobody will need to re-sign by themselves for that matter. Unless they want it, of course.

[FernandoMiguel]

you can open Application, click app and Option and it will allow you to execute. that's why i upgraded mine

[MaxDesiatov]

@FernandoMiguel I know about that, that's what I meant by "give an exemption to this single binary". I'm not doing that for any binary under any circumstances due to security reasons, as I mentioned. In no way I'm suggesting that this binary contains any malware, I just think that rebuilding from sources and signing with my own cert is more secure than a habit of giving exemption to any binaries.