I'm getting a code signing crash when I try to register a helper app as a login item, and I think this is new with macOS 13.4. That is, the crash log contains this:
Exception Type: EXC_CRASH (SIGKILL (Code Signature Invalid))
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: CODESIGNING 4 Launch Constraint Violation
I'm seeing one suspicious message in the system log:
tccd Prompting policy for hardened runtime; service: kTCCServiceAppleEvents requires entitlement com.apple.security.automation.apple-events but it is missing for accessing={TCCDProcess: identifier=com.jwwalker.AutoPairs.uiapp,
pid=91471, auid=501, euid=501, binary_path=/Applications/AutoPairs 4.0.1a1/AutoPairs4.0.1a1.app/Contents/MacOS/AutoPairs}, requesting={TCCDProcess: identifier=com.apple.appleeventsd, pid=531, auid=55, euid=55, binary_path=/System/Library/CoreServices/appleeventsd},
I can't figure out why the OS would think that I need an Apple Events entitlement.
I've looked a the thread Resolving Code Signing Crashes on
Launch, but it hasn't enlightened me. One problem I ran into is at the step
certtool d "authorised0.cer"
I get the output
CSSM_CL_CertGetAllFields: CSSMERR_CL_UNKNOWN_FORMAT
Hi! I am currently trying to upload my iOS app to App Store Connect. Unfortunately, code signing fails with the following error: "Code object is not signed at all.", referencing a binary Metallib (created with metal-tt and an mtlp-json script). I am using Xcode's automatically managed signing and the binary metallib is located inside the "Resources" directory of a framework that I am including with "Embed and sign" in the app. Could anyone give some guidance on what I need to change to make code signing work? Thank you.
I am working on an open source weather app for distribution outside the Mac App store: https://sourceforge.net/projects/heat-meteo
The project builds and runs fine in Xcode.
The batch build script was using ALTOOL which can’t/shouldn’t be used anymore. I am trying to set it up for notarytool.
This is what I think is now happening.
Again, all works fine in the Xcode debugger.
In Xcode, the build is setup with Automatically manage signing for both Debug and Release. They are using my Apple Development account, 4V7….
What I have read if that if I want to distribute outside of the Mac App store, it must be signed with my Developer ID Application, 7VN….
I tried to do an xcodebuild then codesign to switch from 4V7 to 7VN. That actually worked. codesign -dv --verbose=4 shows the correct account. However when I do that, codesign --display --verbose shows I lost the hardened runtime and then notarytool fails because hardened runtime isn’t set. The hardened runtime flag IS set before the codesign command.
I can physically turn off Automatically manage signing in Xcode for Release, but how to I select my Developer ID Application account? It does not appear to be a choice.
If it matters, the application needs both WeatherKit and Location entitlements and they are set to YES in the entitlements file.
I’m guessing, and this pure guessing, I need to adjust something in https://developer.apple.com/account but I don’t know what.
Thanks in advance.
Ed
Post not yet marked as solved
I have a individual team with my dev account. I have recently got an invite for another team. I accepted the invite and now I need to sign the application and upload for that team.
The new team however is not showing up in Xcode as an option and only shows my individual team.
How do I get the new team added as an option within Xcode?
Post not yet marked as solved
We develop a system that can open frameworks which are located in document path in iPads by use "dlopen method" (iPadOS v15)
It works fine when we build the app in device or use "development method" to archive the APP.
But When we try to release our enterprise by use "in-house method" to archive the APP.
Then the error message shows "dylib: file system sandbox blocked mmap()" when our enterprise APP try to open the framework in the APP`s document sandbox.
Why it is able to use this dlopen method under "development method" but is not able to work in "in-house method" ?
Is there any restriction of use "dlopen" by distribution release of enterprise program?
Post not yet marked as solved
Hi!
We're using AdHoc builds for internal testing and that worked fine for the last couple of years.
Recently, we've noticed that the installation of those builds fails on all devices that have iOS 16.4 or iOS 16.5 installed. When tapping on the icon, iOS shows an alert saying "Unable to Install APPNAME. This app cannot be installed because its integrity could not be verified"
The same builds can be installed normally on all devices that are still on 16.1, 16.2 or 16.3. We're building using Xcode 14.3, devices are registered correctly and developer mode is enabled everywhere.
Did someone else run into this issue?
Thanks,
Klemens
Hi,
So I am bundling a FileProvider Extension with my electron application and have noticed a very strange behavior. When I package my application and install/launch it from any directory everything runs perfect. However the exception is when I install it to/launch it from the /Applications folder.
Specifically I receive Cannot create domain: Error Domain=NSFileProviderErrorDomain Code=-2001 "The application cannot be used right now." which maps to providerNotFound. Seems that the provider is failing to instantiate altogether, and therefore I lack any extension functionality.
After I have run the app from the /Applications folder once if I try and run the app from any other directory it fails and I get the same error message.
Anybody have any clues as to what may be changing in my environment that driving this behavior?
Post not yet marked as solved
The .NET Runtime has shipped an lldb extension that looks to extend LLDB functionality to be able to reason about .NET managed code. This has been working for a long time, but now it fails to load with the error error: this file does not represent a loadable dylib. Loading works if I use a self-compiled version of LLDB. I can't really debug XCode's LLDB, but there are some logs that seemed to hint it was signing checks failing for library validation, but neither Developer nor Application signing would satisfy these. LLDB resides within the XCode bundle at /Applications/Xcode.app/Contents/Developer/usr/bin/lldb. codesign confirms that the bundle enforces library validation. Is there any way to confirm this is the issue? It looks like:
Library Validation failed: Rejecting '/*/libsosplugin.dylib' (Team ID: none, platform: no) for process 'lldb(77691)' (Team ID: none, platform: yes), reason: mapped file has no Team ID and is not a platform binary (signed with custom identity or adhoc?)
and
Library Validation failed: Rejecting '/*/libsosplugin.dylib' (Team ID: UBF8T346G9, platform: no) for process 'lldb(77691)' (Team ID: none, platform: yes), reason: mapping process is a platform binary, but mapped file is not
If that's the issue, what's the suggested way forward to have loadable lldb plugins? If not, what's the recommended way to diagnose this? lldb logging is verbose, but doesn't provide any information around this.
Post not yet marked as solved
General:
DevForums tags: Code Signing, Signing Certificates, Provisioning Profiles, Entitlements
Developer Account Help — This document is good in general but, in particular, the Reference section is chock-full of useful information, including the names and purposes of all certificate types issued by Apple Developer web site, tables of which capabilities are supported by which distribution models on iOS and macOS, and information on how to use managed capabilities.
Entitlements documentation
TN3125 Inside Code Signing: Provisioning Profiles — This includes links to other technotes in the Inside Code Signing series.
Certificate Signing Requests Explained DevForums post
--deep Considered Harmful DevForums post
Don’t Run App Store Distribution-Signed Code DevForums post
Resolving errSecInternalComponent errors during code signing DevForums post
Mac code signing:
DevForums tag: Developer ID
Placing Content in a Bundle documentation
Embedding Nonstandard Code Structures in a Bundle documentation
Embedding a Command-Line Tool in a Sandboxed App documentation
Signing a Daemon with a Restricted Entitlement documentation
TN2206 macOS Code Signing In Depth archived technote — This doc has mostly been replaced by the other resources linked to here but it still contains a few unique tidbits and it’s a great historical reference.
Creating Distribution-Signed Code for Mac DevForums post
Packaging Mac Software for Distribution DevForums post
Manual Code Signing Example DevForums post
For problems with notarisation, see Notarisation Resources. For problems with the trusted execution system, including Gatekeeper, see Trusted Execution Resources.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
Hello all!
My project ic C++ project with CMake and need to create in CMakeLists.txt functionality of automatic code sign for specific team and product. Is there any way to do it?
Is there any examples or manuals?
My CMake is 3.26.3
Post not yet marked as solved
Hi,Guys!!
I am useing Unity build my ios project, builds and running in xcode without any issues.
But,when i use 'archive' excute build and submit to app store, An error has occurred in xcode,
prompts me 'Missing signing identifier at libswiftCore.dylib'
I used the follwing librarys.
Firebase,Applovin,StoreKit,AppsFlyer,AuthenticationService.framework
I've searched many sites,but i can't find any help.
Please give me some advice
Thanks a lot !!!!
Thanks a lot !!!!
Thanks a lot !!!!
Missing signing identifier at "/var/folders/qz/fqrs14ws2737g8jpqysndqqw0000gn/T/XcodeDistPipeline.~~~zYHleI/Root/Payload/8BallKing.app/Frameworks/UnityFramework.framework/Frameworks/libswiftCore.dylib".
Failed to cloud sign "/var/folders/qz/fqrs14ws2737g8jpqysndqqw0000gn/T/XcodeDistPipeline.~~~zYHleI/Root/Payload/8BallKing.app/Frameworks/UnityFramework.framework/Frameworks/libswiftCore.dylib". Please file a bug report at https://feedbackassistant.apple.com.
Post not yet marked as solved
I have signed Safari app using product-> archive with automatic sign option using developer ID and notarised to distribute out side of App Store.
Finally , I have observed that Safari is showing extension only in develop mode by selecting allowing unsigned apps option.
why safari treating properly signed as unsigned ? Is my understanding correct?
Post not yet marked as solved
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
Post not yet marked as solved
I have some issues linking some frameworks when I run my iOS application. The issue comes as code signing version is not supported. I use Carthage for the dependency management. It links the framework then has the copy-framework script where it copies to the framework and does the code signing.
For code signing it does the same thing codesign --force --sign ****** --preserve-metadata=identifier,entitlements path_to_framework
The CodeDirectory for some frameworks after signing is 20200 and for others 20400. Obviously 20200 is not supported anymore hence the issue, although I don’t under why does it assign an old version number to it when it's been signed the same way in Big Sur.
I have Xcode 12.3 and using Big Sur 11.4.
Framework where it’s not working:
Executable=********/Frameworks/FirebaseCore.framework/FirebaseCore
Identifier=com.firebase.Firebase-FirebaseCore
Format=bundle with generic
CodeDirectory v=20200 size=226 flags=0x0(none) hashes=1+3 location=embedded
Signature size=4886
Signed Time=18 Jun 2021 at 16:15:27
Info.plist entries=7
TeamIdentifier=********
Sealed Resources version=2 rules=10 files=1
Internal requirements count=1 size=196
Framework where the code signing works properly:
Executable=********/Frameworks/RxSwift.framework/RxSwift
Identifier=io.rx.RxSwift
Format=bundle with Mach-O universal (arm64)
CodeDirectory v=20400 size=74833 flags=0x0(none) hashes=2332+3 location=embedded
Signature size=4886
Signed Time=18 Jun 2021 at 16:16:07
Info.plist entries=21
TeamIdentifier=********
Sealed Resources version=2 rules=10 files=0
Internal requirements count=1 size=176
Any idea what the issue can be?
I have used Xcode for app signing since its inception. Before that, I managed signing like everybody else did - manually. Today I uploaded the iOS version of my app fine, but when I tried to upload the macOS version, I got the following.
Invalid Provisioning Profile Signature. The provisioning profile included in the bundle com.blablabla.BlaBla [com.blablaba.BlaBla.pkg/Payload/BlaBla.app] cannot be used to submit apps to the Mac App Store until it has a valid signature from Apple. For more information, visit the macOS Developer Portal.
This is the first time that I've gotten this error. I am probably missing something simple. At least, I hope that I am. Can anybody help me? I am using Xcode 14.3.
Post marked as Apple Recommended
Developing a ios app in Unreal Engine 5. Everything was alright. Until it wasn’t.
Build to iOS device. Click. Cooking. Building… “ERROR: CodeSign Failed”
D4mn it! hahaha
Here’s the log:
UATHelper: Packaging (IOS): Command CodeSign failed with a nonzero exit code
UATHelper: Packaging (IOS): ** BUILD FAILED **
UATHelper: Packaging (IOS): The following build commands failed:
UATHelper: Packaging (IOS): CodeSign /Users/jordansktorres/My\ Drive/PROJECTS/CRUZEIRO-DO-SUL/ValenteGO/ValenteGO_V1/Binaries/IOS/Payload/ValenteGO_V1.app (in target ‘ValenteGO_V1’ from project ‘ValenteGO_V1’)
UATHelper: Packaging (IOS): (1 failure)
UATHelper: Packaging (IOS): Took 12,659139s to run env, ExitCode=65
UATHelper: Packaging (IOS): ERROR: CodeSign Failed
UATHelper: Packaging (IOS): (see /Users/jordansktorres/Library/Logs/Unreal Engine/LocalBuildLogs/Log.txt for full exception trace)
UATHelper: Packaging (IOS): AutomationTool executed for 0h 1m 51s
UATHelper: Packaging (IOS): AutomationTool exiting with ExitCode=32 (Error_FailedToCodeSign)
UATHelper: Packaging (IOS): RunUAT ERROR: AutomationTool was unable to run successfully. Exited with code: 32
PackagingResults: Error: Failed to Code Sign
I have deleted the binaries, build, intermediate, and saved folders. I have generated and created new certificates. I have deleted UE5 and re-install it again. I have thrown the project into the garbage can and created a whole new project file with the same content folder. It all led to the same result. “ERROR: CodeSign Failed”
Please, someone, anyone, give me a light here. hahaha
Post not yet marked as solved
Hello. I have an iOS app written in Xamarin, but this issue is not related to Xamarin or Visual Studio. I am trying to deploy my xamarin app onto an iOS device, but I am unable to get the iOS device to install the provisioning profile via Xcode. I work at a company with a decent variety of test devices and the result seems to be the same from iPads to iPods to iPhones of various ages.
I have created a certificate and a provisioning profile. The certificate is associated with the provisioning profile on the developer portal. I have imported the certificate (including private keys) into my login keychain on MacOS. I have the .mobileprovision file downloaded to the machine. I am signed into Xcode with my apple developer account.
In Xcode, i went to Window > Devices and Simulators and selected my device. I right clicked my device and selected "Show Provisioning Profiles". I clicked the plus and chose my .mobileprovision file. I get the same error on every device:
Failed to install one or more provisioning profiles on the device.
Please ensure the provisioning profile is configured for this device. If not, please try to generate a new profile.|
this is an incredibly vague and unhelpful error. I'm not really sure what it means by "configured for this device". Not sure where to go from here
Post not yet marked as solved
I'm signing using "Developer ID Application" and it suddenly started failing due to the following reason A timestamp was expected but was not found.. from the logs it looks like a failure to connect Apple's dedicated server. Perhaps there's a way to verify this theory, or get another timestamp server to be set in --timestamp option?
thanks
2023-04-24 15:53:38.977560+0300 0x2e29ef5 Error 0x0 696 0 XPCTimeStampingService: (CFNetwork) NSURLConnection finished with error - code -1001
2023-04-24 15:53:38.977753+0300 0x2e29ef5 Default 0x0 696 0 XPCTimeStampingService: (CFNetwork) [com.apple.CFNetwork:Summary] Task <42F5893A-941A-4293-BB14-F75C42363836>.<0> summary for task failure {transaction_duration_ms=15792, response_status=-1, connection=817, reused=1, request_start_ms=0, request_duration_ms=0, response_start_ms=0, response_duration_ms=0, request_bytes=0, response_bytes=0, cache_hit=false}
I'm signing an app like this:
% codesign --entitlements entitlements.xml --sign "My Cert" AppName
% codesign -dv --verbose=4 AppName.app
and I was rather hoping that the -dv check would be sufficient for macOS to verify the signature but when I immediately attach lldb and start the process, Finder pops up "Verifying AppName..." and then after some time lldb fails and logs error: Tried to attach to process already being debugged.
If I manually wait for the verification popup to disappear then I can attach lldb just fine and run the LLDB script I want to use to extract information from the app.
How can I either run the signature verification on the command line or (without a sleep hack) have LLDB wait?
Post not yet marked as solved
i have some code signing problems, i want someone help me
JWWalker.
