Yeah, hit me up with this, I have the 13 beta and maintain iTerm2. iTerm2 is getting harder and harder to maintain as a port - I'm starting to wonder if it might be worthwhile to just download the correct binary, or just abandon it as a port. I don't like the idea of abandoning it as a port - but it causes a lot of problems.
—Mark _______________________ Mark E. Anderson <[email protected]> MacPorts Trac WikiPage <https://trac.macports.org/wiki/mark> GitHub Profile <https://github.com/markemer> On Tue, Jun 14, 2022 at 3:23 AM Zhenfu Shi <[email protected]> wrote: > Hi all, > It’s probably too early to talk about this but I would like to share > something I found playing with the newest beta OS. > When trying to get iTerm2 port to build on macOS 13, Xcode spits out error > "An empty identity is not valid when signing a binary for the product type > [type]”. Previously to avoid signing problems, I or someone else had the > identity removed, effectively disabling code signing. This apparently no > longer works, and I had to use the adhoc signing identity “-“ for it to > build. > This could affect a number of ports that are using Xcode to build apps, so > I figured people here should know. > > Zhenfu
