Bug Missing signing identifier at

Hello friends. I'm going to upload a game to the appstore, but I'm getting such an error and I couldn't find a solution. Xcode is up to date

 

I'm having the same issue. Were you able to figure out what the problem was?

 

same issue here. No solution found so far.

 

Error is gone after setting the min target to iOS 15 in xcode.

 

I'm having the same problem! Started after upgrading to Xcode 14.1, Unity 2020.3.41 and Facebook SDK 14.1.
The "one weird trick" mentioned at https://forum.unity.com/threads/xco...fier-at-unity-framework.1266758/#post-8528231 does indeed work, but it's suspicious and manual.

I wish I could understand what's going on and fix it permanently and at the source.

 

@DarekRusin I explained why the "weird trick" works on my other comment here: https://forum.unity.com/threads/xco...fier-at-unity-framework.1266758/#post-8930493

Now I just want to know if ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES is set to YES by default for UnityFramework or is there a library like https://github.com/googlesamples/unity-jar-resolver that is setting it to YES (I haven't got time to dig through their source code).

 

I have a vague recollection that we've eventually linked this to the changes in Facebook SDK, which at some point started adding pieces of Swift code and then in turn, it seems that Unity, upon seeing any traces of Swift code, forces ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES to YES. Here's the relevant comment from them:

> yeah, we have code that forcibly set it to YES if .swift file is encountered. essentially we have this:

source: https://forum.unity.com/threads/set...aries-to-no-doenst-work.1314210/#post-8314440

In the end we ended up with the same solution as you did in the linked comment and we're setting the flag to NO in a postprocess step:

Code (CSharp):

1. proj.SetBuildProperty(unityFrameworkTargetGuid, "ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES", "NO");

Just make sure that your postprocess step priority is high enough so that other SDKs won't override your override. We've been bitten by this too