Fix so people with macs can download the dmg, copy Mb2 into applications and run it.
It turns out, I have never actually tried doing that. In the past, I was having the build process copy the Mb2.app artifact into /Applications and that's simply what I would run. Eventually, after the updater was working, I'd use the updater to update and that also worked. So I have been assuming that anyone who downloaded the dmg and copied the app would have a working app, however when I actually did that, I was told that Mb2.app was corrupted.
I have not yet researched if there is a difference between the artifact that's built and the artifact in the dmg. That's logically the first step, because if the two are byte-per-byte the same, then it's not a problem with the .app itself, but some aspect of how macOS judges it. If there is a difference, then the question is what is the difference, how does it creep in and why does it make macOS think the binary is corrupted.
Fix so people with macs can download the dmg, copy Mb2 into applications and run it.
It turns out, I have never actually tried doing that. In the past, I was having the build process copy the Mb2.app artifact into /Applications and that's simply what I would run. Eventually, after the updater was working, I'd use the updater to update and that also worked. So I have been assuming that anyone who downloaded the dmg and copied the app would have a working app, however when I actually did that, I was told that Mb2.app was corrupted.
I have not yet researched if there is a difference between the artifact that's built and the artifact in the dmg. That's logically the first step, because if the two are byte-per-byte the same, then it's not a problem with the .app itself, but some aspect of how macOS judges it. If there is a difference, then the question is what is the difference, how does it creep in and why does it make macOS think the binary is corrupted.