Opened 2 years ago
Last modified 2 years ago
#64322 assigned defect
TeXShop4 @4.68: Build fails due to code signing error
| Reported by: | mrkrause (Matthew Krause) | Owned by: | Schamschula (Marius Schamschula) |
|---|---|---|---|
| Priority: | Low | Milestone: | |
| Component: | ports | Version: | 2.7.1 |
| Keywords: | code signature | Cc: | Schamschula (Marius Schamschula) |
| Port: | TexShop4 |
Description
My initial build of TexShop4 failed due to a code signing error.
The Xcode Project is trying to sign the binary with credentials belonging to Richard Koch, the program's author (ID: RBGCY5RJWM), which I obviously don't have. To fix the problem, I signed into my AppleID account in Xcode (Xcode -> Preferences -> Accounts) and pressed "Download Manual Profiles" at the bottom. After doing so, I changed the Team ID in the "Signing and Capabilities tab" from the red RBGCY5RJWM to my own name. The build then proceeded successfully.
I haven't been able to reliably reproduce this: Xcode seems to cache the signing profile somewhere and subsequent uninstall/reclaim/install cycles worked without intervention. I didn't save the initial error message, but it was the final build step. The offending Team ID also shows up in several places in the build directory.
Attachments (1)
Change History (6)
Changed 2 years ago by mrkrause (Matthew Krause)
| Attachment: | Screen Shot 2021-12-30 at 12.36.15 PM.png added |
|---|
comment:1 Changed 2 years ago by Schamschula (Marius Schamschula)
| Owner: | set to Schamschula |
|---|---|
| Status: | new → assigned |
Very strange.
This is a well known issue with TeXShop.
comment:2 Changed 2 years ago by Schamschula (Marius Schamschula)
The xcode.build.settings, i.e. CODE_SIGN_IDENTITY=, should take care of this.
comment:3 follow-up: 5 Changed 2 years ago by mrkrause (Matthew Krause)
I remember seeing that at the tail end of the failed build (and the variable was equal to nothing/blank, rather than RBGCY5RJWM).
Don't you need to be signed into an AppleID for code signing to work at all? This happened on a fresh Xcode install after a big upgrade (MacOS 10.15 -> 12.1), so I was definitely signed out of my Apple account during the failed build. After it worked once, I tried signing out of my account and reinstalling, which worked. I also tried reinstalling it via a new (system) user, which presumably would not have had access to the same Xcode profile. That worked too, so I'm stumped.
Anyway, I'll take more detailed notes if this occurs again. In the meantime, I hope the steps are useful to anyone else with a similar problem.
Thanks again for keeping this running and happy holidays.
comment:4 Changed 2 years ago by Schamschula (Marius Schamschula)
I see no such issue on my Big Sur build machine.
comment:5 Changed 2 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to mrkrause:
Don't you need to be signed into an AppleID for code signing to work at all?
The buildbot machines, which have never had Xcode signed in to any Apple ID, seem to be able to build the port.
Screenshot of Xcode