The code signature version is no longer supported.
calioptrix opened this issue · comments
Checklist before submitting a bug report
- I've updated to the latest released version of the SDK
- I've searched for existing GitHub issues
- I've looked for existing answers on Stack Overflow, the Facebook Developer Community Forum and the Facebook Developers Group
- I've read the Code of Conduct
- This issue is not security related and can safely be disclosed publicly on GitHub
Xcode version
12.4 (12D4e)
Facebook iOS SDK version
12.3.1
Dependency Manager
SPM
SDK Framework
Core
Goals
install an app using the framework onto iphone with ios15
Expected results
app should build and run on the iphone
Actual results
When attempting to run the app on an actual phone, it gives an error unable to install. The details button says this:
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 0x000000012878dc8f DTDKCreateNSErrorFromAMDErrorCode + 220
1 DTDeviceKitBase 0x00000001287cc241 __90-[DTDKMobileDeviceToken installApplicationBundleAtPath:withOptions:andError:withCallback:]_block_invoke + 155
2 DVTFoundation 0x000000010d61864b DVTInvokeWithStrongOwnership + 71
3 DTDeviceKitBase 0x00000001287cbf82 -[DTDKMobileDeviceToken installApplicationBundleAtPath:withOptions:andError:withCallback:] + 1440
4 IDEiOSSupportCore 0x000000012863ca10 __118-[DVTiOSDevice(DVTiPhoneApplicationInstallation) processAppInstallSet:appUninstallSet:installOptions:completionBlock:]_block_invoke.292 + 3513
5 DVTFoundation 0x000000010d74717e DVT_CALLING_CLIENT_BLOCK + 7
6 DVTFoundation 0x000000010d748da0 __DVTDispatchAsync_block_invoke + 1191
7 libdispatch.dylib 0x00007fff737b46c4 _dispatch_call_block_and_release + 12
8 libdispatch.dylib 0x00007fff737b5658 _dispatch_client_callout + 8
9 libdispatch.dylib 0x00007fff737bac44 _dispatch_lane_serial_drain + 597
10 libdispatch.dylib 0x00007fff737bb5d6 _dispatch_lane_invoke + 363
11 libdispatch.dylib 0x00007fff737c4c09 _dispatch_workloop_worker_thread + 596
12 libsystem_pthread.dylib 0x00007fff73a13a3d _pthread_wqthread + 290
13 libsystem_pthread.dylib 0x00007fff73a12b77 start_wqthread + 15
);
}
System Information
macOS Version 10.15.7 (Build 19H1713)
Xcode 12.4 (17801) (Build 12D4e)
Timestamp: 2022-02-05T23:10:40-05:00
there are two relevant stack overflow posts regarding this:
https://stackoverflow.com/questions/68467306/the-code-signature-version-is-no-longer-supported
https://stackoverflow.com/questions/68931476/this-code-signature-is-no-longer-supported-when-building-app-on-iphone-12
Adding the --generate-entitlement-der option to build settings works for a blank project. As soon as the facebook sdk is added from File > Swift Packages the project will not run.
It is suggested to set the framework to "do not embed" but the "embed" column under project > target > general > Frameworks, libraries, and embedded content is blank. It only shows the names of the frameworks. xcode does not state if the frameworks are embedded, and there is no option to specify whether it should be embedded or not.
Steps to reproduce
create a blank project. add the facebook sdk from File > Swift Packages
Code samples & details
No response
Hi @calioptrix - This issue was previously reported in #1924 but we weren't able to reproduce it.
You mentioned that this is occurring with a new blank project, however we weren't able to reproduce it with a blank project. Can you attach that project that it's occurring with for you, so that we can take a closer look?
Also could you try upgrading to Xcode 13 to see if this issue still occurs?
Attached is a blank project that does not run once the facebook sdk is included.
Steps to reproduce:
File > New Project
Choose App
Set product name to "facebooksdktest"
Uncheck "use core data" just so there's less in the project
Add --generate-entitlement-der option using answer from Lance Samaria in the first stack overflow link I provided
Connect phone and run to verify that the app runs properly
File > swift packages > add package dependencies
paste in url https://github.com/facebook/facebook-ios-sdk
Check boxes for FacebookBasics, FacebookCore, FacebookLogin, FacebookShare
Try to run project again
I am unable to upgrade to xcode 13 as it requires macOS 11. I have a 2012 iMac and 2012 mac mini. Both are limited to macOS 10. I am experiencing the same issue on both systems.
Hi, this issue happens when you add FBAudienceNetwork xcframework static file into the project and run on device.
I created a repo that reproduce this issue. This issue also happening on XCode 13.2.1.
https://github.com/ozcanzaferayan/fbaudience-issue-code-signature-version
@calioptrix - I used the project you provided but didn't have an issue in running the app on my device. However, I did just notice that you are using Xcode 12.4 but the binaries are built with Xcode 12.5 so that would be the minimum version of Xcode that would be supported to use with the binaries, so unfortunately you may not be able to update until you can update your version of Xcode to at least 12.5 for the current release.
@ozcanzaferayan - I was able to reproduce the issue with the project you provided, however, our team does not support FBAudienceNetwork, we only support the iOS SDK. You can report a bug for the AudienceNetwork team using https://developers.facebook.com/support/bugs/. I also noticed that your project included FBAudienceNetwork 6.2 while the current version is 6.9.0. Perhaps you can try upgrading to see if that helps.
https://developers.facebook.com/docs/audience-network/setting-up/platform-setup/ios/add-sdk
Xcode 12.5 also requires macOS 11. I was able to use OpenCore Legacy Patcher (https://github.com/dortania/OpenCore-Legacy-Patcher) to upgrade to macOS11. Xcode 13 could then be installed. The test project now runs. I was able to remove the --generate-entitlement-der setting and it still runs.
@calioptrix - Thanks for the update. I'm glad that you were able to upgrade and especially to give us confirmation that upgrading worked for other developers that might search for this issue.