the version 1.2 binary is ARM / AppleSilicon only and cannot be launched on Intel Macs. is this on-purpose? if so, i didn't see any anouncement about dropping Intel-compatibility in the release-notes...
No, this was not on purpose. We use the latest macos-runner on Github, and that is now using M1.
I will setup a new build explicitly running on Intel macos.
We don't currently have any developers or testers with a mac. Please do tell, or join our Discord, if you could help test other fixes for macos-only problems.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@stiangre i can confirm this is a valid build for Intel. i did have issues launching it due to the Ad-hoc signature. even the normal workaround "right click => open" did not work. however the build launched and worked fine after manually removing the quarantine from the command-line
@julianmayer:
Yes, this is known. These are files from the Java runtime that is included in our package. The suggested solution is just signing everything again.
However, I don't want to annually pay Apple to have a developer account just in order to distribute free software on their closed ecosystem.
Using an adhoc signature did not help the last time I tried, but please do test and report back if this now helps: codesign --force -s - --deep FILE
It might be possible to create a self-signed certificate and have this work (albeit still with a warning). I could try this out if someone writes out the commands needed for generating the signature and for using that signature for signing the dmg-file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
since i have already launched it on that Mac using the Terminal workaround i cannot tell you if resigning helpts with the launch issue. it definitely gets rid of the "code-signature of app is invalid" message though
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No, this was not on purpose. We use the latest macos-runner on Github, and that is now using M1.
I will setup a new build explicitly running on Intel macos.
We don't currently have any developers or testers with a mac. Please do tell, or join our Discord, if you could help test other fixes for macos-only problems.
@julianmayer: I have built a new package that should work on Intel macOs:
Download FreeCol 1.2.0 (Intel)
@stiangre i can confirm this is a valid build for Intel. i did have issues launching it due to the Ad-hoc signature. even the normal workaround "right click => open" did not work. however the build launched and worked fine after manually removing the quarantine from the command-line
launch issue is probably because the signature is not just ad-hoc but also invalid:
@julianmayer:
Yes, this is known. These are files from the Java runtime that is included in our package. The suggested solution is just signing everything again.
However, I don't want to annually pay Apple to have a developer account just in order to distribute free software on their closed ecosystem.
Using an adhoc signature did not help the last time I tried, but please do test and report back if this now helps:
codesign --force -s - --deep FILEIt might be possible to create a self-signed certificate and have this work (albeit still with a warning). I could try this out if someone writes out the commands needed for generating the signature and for using that signature for signing the dmg-file.
since i have already launched it on that Mac using the Terminal workaround i cannot tell you if resigning helpts with the launch issue. it definitely gets rid of the "code-signature of app is invalid" message though