Toolchain packages over the last month have had invalid signing, making them fail to open after double clicking. Manually opening the package (or removing the quarantine attribute, I assume) lets it install, but that could be a dangerous step. Can this be fixed?

CC @mishal_shah

I posted this here since previous signing topics have been here. Feel free to move it somewhere more appropriate if necessary.

1 Like

@Jon_Shier can share the link to the toolchain you are seeing this issue with? Thanks!

All of the latest toolchains, including the trunk toolchain from 6/13 and the 5.6 snapshots from 6/13 and 6/23.

The 6/26 5.5 toolchain seems to have valid signing.

I aggreed.

The latest toolchains from today seem to have this same problem for me…