macOS Signed Sandbox Builds now require Apple Development Certificate

UNSH / Unity-Apple-Distribution-Workflow

Workflow to automate prepare Unity builds for in -or outside of the Appstore. A folder chronology with instructions, guides, templates, and scripts to finalise Unity builds for Apple from start to finish.

https://unsh.github.io/Unity-Apple-Distribution-Workflow/

35 stars 6 forks source link

macOS Signed Sandbox Builds now require Apple Development Certificate #8

Open danoli3 opened 4 years ago

danoli3 commented 4 years ago

Apple have changed recently the signing for Developer Signed Sandbox builds to no longer use the "Mac Development" Certificate in favour of the new iOS/tvOS/macOS Shared Developer "Apple Development" Certificate.

Using the Mac Development certificate causes code signing issues on Catalina with Xcode 11.2

This was a recent change last Wednesday.

omgitsraven commented 4 years ago

Thanks for clarifying this! I just ran into this recently and couldn't figure out why Xcode was using this "Apple Development" certificate all of a sudden...

Luckily it's an easy fix for people using the process, just find-and-replace "Mac Developer" to "Apple Development" in the script... I'm not sure how it should be handled for the main repo though, if we don't want to break support for people who are still on the old certificates (mine didn't change over until this week!)

v01pe commented 4 years ago

Not currently using this any more, but the "automatic" workflow could check against xcode-select --version – this currently returns – for Xcode version 11.5 (11E608c)

xcode-select version 2373.

What's this version number for 11.2?