The LibO 220.127.116.11 main package (LibreOffice.app) for macOS is not signed.
The effect is that Gatekeeper on macOS does not allow starting the app (unless you bypass it).
This is a regression.
Please note that you have to bypass Gatekeeper only once (for those of you who want to reproduce the bug).
Further note: as of right now, I cannot select 18.104.22.168 as the affected LibO version in bugzilla (entry is still missing).
Steps to Reproduce:
1.install LibO on macOS
2.start the app
3.you have to bypass Gatekeeper in order for the app to be allowed to start
LibO only starts if you bypass Gatekeeper.
This is bad behaviour, all macOS apps should be digitally signed by a verifyable developer.
LibreOffice.app should by digitally signed. It should be startable even if Gatekeeper is set to its strictest settings.
User Profile Reset: No
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:50.0) Gecko/20100101 Firefox/50.0
Confirming with LO53b2
Not sure what the policy is here - my uderstanding was that DEV releases (which is what 53beta2 still is, were not signed.
Altered priority and importance pending Christian's reply
Norbert - prolly right up your street =)
All officially provided builds should be signed, no matter whether it is LibreOfficeDev variant or in release candidate configuration (as the reporter reports against 22.214.171.124, which is no longer LibreOfficeDev, but LibreOffice proper).
$ codesign -v Desktop/LibreOffice.app
Desktop/LibreOffice.app: code object is not signed at all
In architecture: x86_64
thus confirming and reassigning to Norbert, who actually does the build. Likely just using wrong autogen.input, no problem with the process as a whole.
fixed in LO 126.96.36.199