sign to run locally does not work

Question

Created Jan ’23

Replies 1

Boosts 0

Views 3.3k

Participants 2

I have an app and a dylib building in the same workspace. When I choose "Development" as the signing cert everything works. However, when XCode updates, it always asks me to convert to the recommended settings which is to sign to run locally. This has never worked. It says:

'.../Developer/Xcode/DerivedData/SwiftProjects-chxoucgxvsdfbvddpvzzmkrojpay/Build/Products/Debug/Common_swift.framework/Versions/A/Common_swift' not valid for use in process: mapping process has no Team ID and is not a platform binary)

However, the dylib is signed with my team and signing certificate "Development". If I change the dylib to also sign to run locally I get the same message.

Not a huge issue since it works fine with my developement signature, but it is annoying.

Boost

Answer 1

DTS Engineer OP

Apple

Jan ’23

For day-to-day development, I recommend Apple Development signing for all your code. Sign to Run Locally is Xcode’s name for ad hoc signing [1] which leaves your code without a stable designated requirement. A stable DR is important for the reasons I outline in TN3127 Inside Code Signing: Requirements.

However, when Xcode updates, it always asks me to convert to the recommended settings which is to sign to run locally.

Weird. It shouldn’t be doing that. You should definitely decline that recommendation. I also encourage you to file a bug about this. Please post your bug number, just for the record.

FWIW, I tried to reproduce this here in my office and couldn’t. Specifically, I used Xcode 14.1 to create a dynamic library project and then opened it in Xcode 14.2 and got no upgrade notice. Having said that, I have experience exactly the behaviour you’re seeing and, yeah, it’s kinda annoying.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] This is different from iOS’s Ad Hoc distribution.

0