Xcode 12.5 "code signature version is no longer supported"

Developer Tools & Services Xcode
bumbleparrot OP
Created Apr ’21
Replies 25
Boosts 1
Views 37k
Participants 36
After upgrading to Xcode 12.5 and iOS 14.5, I can no longer debug my app on my local physical device.

I get the below error.

I searched and cannot find any answers.

How do I fixed this?

Details

Unable to install "MyApp"
Domain: com.apple.dt.MobileDeviceErrorDomain
Code: -402620375

  • -

The code signature version is no longer supported.
Domain: com.apple.dt.MobileDeviceErrorDomain
Code: -402620375
User Info: {
  DVTRadarComponentKey = 261622;
  MobileDeviceErrorCode = "(0xE8008029)";
  "com.apple.dtdevicekit.stacktrace" = (
0  DTDeviceKitBase           0x000000011edd83b8 DTDKCreateNSErrorFromAMDErrorCode + 220
1  DTDeviceKitBase           0x000000011ee16ae1 __90-[DTDKMobileDeviceToken installApplicationBundleAtPath:withOptions:andError:withCallback:]_block_invoke + 155
2  DVTFoundation            0x0000000107881b7c DVTInvokeWithStrongOwnership + 71
3  DTDeviceKitBase           0x000000011ee16822 -[DTDKMobileDeviceToken installApplicationBundleAtPath:withOptions:andError:withCallback:] + 1440
4  IDEiOSSupportCore          0x000000011eccf999 __118-[DVTiOSDevice(DVTiPhoneApplicationInstallation) processAppInstallSet:appUninstallSet:installOptions:completionBlock:]_block_invoke.294 + 3534
5  DVTFoundation            0x00000001079b4931 __DVT_CALLING_CLIENT_BLOCK__ + 7
6  DVTFoundation            0x00000001079b655b __DVTDispatchAsync_block_invoke + 1191
7  libdispatch.dylib          0x00007fff20508603 _dispatch_call_block_and_release + 12
8  libdispatch.dylib          0x00007fff205097e6 _dispatch_client_callout + 8
9  libdispatch.dylib          0x00007fff2050f5ca _dispatch_lane_serial_drain + 606
10 libdispatch.dylib          0x00007fff2051008d _dispatch_lane_invoke + 366
11 libdispatch.dylib          0x00007fff20519bed _dispatch_workloop_worker_thread + 811
12 libsystem_pthread.dylib       0x00007fff206b04c0 _pthread_wqthread + 314
13 libsystem_pthread.dylib       0x00007fff206af493 start_wqthread + 15
);
}

  • -


System Information

macOS Version 11.3 (Build 20E232)
Xcode 12.5 (18205) (Build 12E262)
Timestamp: 2021-04-29T22:41:18-04:00
Replies  25
Boosts  1
Views  37k
Participants  36
BBeing OP
Apr ’21
Same problem.
1
Chokaaaa OP
May ’21
I think its a bug from Xcode same One here, If somebody find Solution tag me :)
0
Claude31 OP
May ’21
Did you try to unregister the device on Xcode and register again ?
1
CopperGaga OP
May ’21
try this way:
go to the TARGETS -> select[your project name] -> General -> Frameworks,Libraries,and EmbeddedContent -> set the framework with [Do Not Embed]
14
PBYorke OP
May ’21
I had to **** DerivedData. I tried both of the before mentioned things so I don't know which one worked.
0
jmstrlr1 OP
May ’21
Hey after struggling with this for an hour or two, I found that in your apple developer account, under 'Certificates, Identifiers & Profiles' > profiles > provisioning profiles, I needed to add the device I was using to test on in there, it takes you through steps. At the end you download a file (file will be named whatever you choose), when downloaded, double click the file and....magic, it works. I've never had this issue until I moved up to Xcode 12.5. Hope it helps.

1
Developer Tools Engineer OP
Apple
May ’21
What’s the output of this command for your app, and any other bundles in your app (ie frameworks, app extensions, etc)?

Code Block 
codesign -dv /path/to/MyApp.app


0
narlei_moreira OP
May ’21
The output of codesign -dv /path/to/MyApp.app:

Code Block 
Executable=/Users/narlei/Library/Developer/Xcode/DerivedData/MyApp-fbfpzfaxsmhnpldccmhdayxtxeuc/Build/Products/Debug-iphoneos/MyApp.app/MyApp
Identifier=br.com.brainweb.MyApp
Format=app bundle with Mach-O thin (arm64)
CodeDirectory v=20400 size=2983545 flags=0x0(none) hashes=93225+7 location=embedded
Signature size=4855
Signed Time=5 May 2021 13:52:46
Info.plist entries=54
TeamIdentifier=XXXXXXXXX
Sealed Resources version=2 rules=10 files=1230
Internal requirements count=1 size=188

0
idelfonso OP
May ’21
Thank you this was my solution to the issue, this error comes out very often regardless of the Xcode version

try this way:
go to the TARGETS -> select[your project name] -> General -> Frameworks,Libraries,and EmbeddedContent -> set the framework with [Do Not Embed]
1
Developer Tools Engineer OP
Apple
May ’21
@narlei_moreira is there a framework in your app as well? What's returned for all the frameworks and app extensions in your app bundle?
0
iosdevuz OP
May ’21
try this way:
go to the TARGETS -> select[your project name] -> General -> Frameworks,Libraries,and EmbeddedContent -> set the framework with [Do Not Embed]
Posted 3 days ago by CopperGaga 

This worked for me! Thank you Copper Gaga
4
Developer Tools Engineer OP
Apple
May ’21
If your apps actually require this embedded content, then removing it may break your release build. Does the framework that's causing this issue have an old signature? You may just need to re-sign it, as explained here.
1
andre-alves646 OP
May ’21
I had this issue and found the solution. It's not about Xcode 12.5, but running on a device with iOS 14.5+.

My project was embedding 2 static frameworks (see @idelfonso answer) and the issue was fixed when I changed them to [Do Not Embed].

However, the correct answer here is not to [Do Not Embed] every framework you have, as you actually need to embed dynamic frameworks, your app will crash upon launch otherwise.

Use 'file' command line to find out if the framework is dynamic or static. For example:

Code Block bash
file Frameworks/Flutter.framework/Flutter
Frameworks/Flutter.framework/Flutter: Mach-O universal binary with 3 architectures: [x86_64:Mach-O 64-bit dynamically linked shared library x86_64] [arm_v7] [arm64]
Frameworks/Flutter.framework/Flutter (for architecture x86_64):	Mach-O 64-bit dynamically linked shared library x86_64
Frameworks/Flutter.framework/Flutter (for architecture armv7):	Mach-O dynamically linked shared library arm_v7
Frameworks/Flutter.framework/Flutter (for architecture arm64):	Mach-O 64-bit dynamically linked shared library arm64


As you can see, in this example Flutter is dynamically linked and therefore needs to be embedded. If 'file' doesn't give any hint that a framework is dynamic, then it's static and should not be embedded.

Embedding static frameworks is wrong because their code is already merged into the final binary. For some reason it was "ok" to do that before iOS 14.5.

Hope this helps.
5
NickYaw OP
May ’21
I think the problem is with the device. Can't run the app on my daily driver but runs fine on a second device.
0
clarkttfu OP
Jul ’21

We use 2 static library in our project. Once the libs were added via "Build Phases > Link Binary with Libraries", they are shown in the "General > Frameworks, Libraries and Embedded Content".

Unlike other frameworks, there is NO "Do Not Embed" option for these 2 static libs. So my guess is they are embedded into the final binary without code signing?

And the problem is only found on the iOS 14.5+ devices.

0
Xcode 12.5 "code signature version is no longer supported"
First post date Last post date
 
 
Q