Code Signing

RSS for tag

Certify that an app was created by you using Code signing, a macOS security technology.

Code Signing Documentation

Pinned Posts

Posts under Code Signing tag

263 Posts
Sort by:
Post not yet marked as solved
2 Replies
34 Views
Hi there, While developing my first kernel extension for a learning purpose, I'm facing the issue above, "Bad code signature". The actual steps to reproduce are as follows: \ Initialize my Xcode project using the template "Generic Kernel Extension". Implement a fundamental extension that displays "Hello World!" using printf();. Build and sign it as "Sign to run locally". Put the "HelloWorld.kext" bundle into the /Library/Extensions/. Change the owner of the bundle file to "root:wheel". Load the extension using as follows. $ cd /Library/Extentions $ sudo kextload /Library/Extensions/HelloWorld.kext Password: Executing: /usr/bin/kmutil load -p /Library/Extensions/HelloWorld.kext Error Domain=KMErrorDomain Code=29 "Authenticating extension failed: Kext com.martymarron.HelloWorld v.1.0.0 in executable kext bundle com.martymarron.HelloWorld at /Library/Extensions/HelloWorld.kext: Authenticating extension failed: Bad code signature" UserInfo={NSLocalizedDescription=Authenticating extension failed: Kext com.martymarron.HelloWorld v1.0.0 in executable kext bundle com.martymarron.HelloWorld at /Library/Extensions/HelloWorld.kext: Authenticating extension failed: Bad code signature} I guessed that the bundle needs to be signed anyway. Hence I signed it for "development", but it resulted in the same. Some article says that my developer account should be enabled for "KEXT development" on https://developer.apple.com/resources/developer-id/, but this link does not work now. Referred article: https://developer.apple.com/forums/thread/30703 Then, I found the article below says "the kernel doesn't load a kext if an equivalent System Extention solution exists". https://developer.apple.com/documentation/kernel/implementing_drivers_system_extensions_and_kexts Does this mean the kernel extension development on my environment is no longer supported? Or is there still the way to try the kernel extension development on my environment? If no, I'll give up trying it and will try "system extension development" instead. Thanks for your kind help! My development environment: OS ver: Monterey(12.5) CPU Arch: Intel Core i7 Xcode ver: Version 13.4.1 (13F100)
Posted Last updated
.
Post not yet marked as solved
3 Replies
179 Views
Hi! I'm trying to move from CoreMedio I/O DAL Plug-In to CoreMedia I/O camera extensions, announced in macOS 12.3. I created a test extension, placed it inside my app bundle into Contents/Library/SystemExtensions and signed with codesigning certificate. But when I try to install my extension from inside my app, using this code (Swift): func requestActivation() { guard case .idle = status else { fatalError("Invalid state") } print("Requesting activation of extension \"\(extensionIdentifier)\"") let req = OSSystemExtensionRequest.activationRequest(forExtensionWithIdentifier: extensionIdentifier, queue: DispatchQueue.main) req.delegate = self OSSystemExtensionManager.shared.submitRequest(req) status = .requested } I'm getting an error: OSSystemExtensionErrorDomain error 8: Code Signature Invalid which is rather generic. Can anybody tell me what I am doing wrong? Or at least propose some steps to find it out? I'm posting here entitlements and codesign output for my extension and containing application for further information. kdg@admins-Mac-mini SystemExtensions % codesign -d --entitlements - ./com.visicom.VirtualCamera.avextension.systemextension Executable=/Applications/VirtualCamera.app/Contents/Library/SystemExtensions/com.visicom.VirtualCamera.avextension.systemextension/Contents/MacOS/com.visicom.VirtualCamera.avextension [Dict] [Key] com.apple.security.app-sandbox [Value] [Bool] true [Key] com.apple.security.application-groups [Value] [Array] [String] 6SUWV7QQBJ.com.visicom.VirtualCamera kdg@admins-Mac-mini /Applications % codesign -d --entitlements - ./VirtualCamera.app Executable=/Applications/VirtualCamera.app/Contents/MacOS/VirtualCamera [Dict] [Key] com.apple.developer.system-extension.install [Value] [Bool] true [Key] com.apple.security.app-sandbox [Value] [Bool] true [Key] com.apple.security.application-groups [Value] [Array] [String] 6SUWV7QQBJ.com.visicom.VirtualCamera [Key] com.apple.security.files.user-selected.read-only [Value] [Bool] true kdg@admins-Mac-mini SystemExtensions % codesign -dvvv ./com.visicom.VirtualCamera.avextension.systemextension Executable=/Applications/VirtualCamera.app/Contents/Library/SystemExtensions/com.visicom.VirtualCamera.avextension.systemextension/Contents/MacOS/com.visicom.VirtualCamera.avextension Identifier=com.visicom.VirtualCamera.avextension Format=bundle with Mach-O universal (x86_64 arm64) CodeDirectory v=20500 size=1553 flags=0x10700(hard,kill,expires,runtime) hashes=37+7 location=embedded Hash type=sha256 size=32 CandidateCDHash sha256=25bd80657bfd6e0ab95467146c7b532817e9e520 CandidateCDHashFull sha256=25bd80657bfd6e0ab95467146c7b532817e9e5209fd50b0cb7ceef40dcfb40e8 Hash choices=sha256 CMSDigest=25bd80657bfd6e0ab95467146c7b532817e9e5209fd50b0cb7ceef40dcfb40e8 CMSDigestType=2 CDHash=25bd80657bfd6e0ab95467146c7b532817e9e520 Signature size=9006 Authority=Developer ID Application: Visicom Media Inc. (6SUWV7QQBJ) Authority=Developer ID Certification Authority Authority=Apple Root CA Timestamp=7 Jul 2022, 21:49:32 Info.plist entries=23 TeamIdentifier=6SUWV7QQBJ Runtime Version=12.3.0 Sealed Resources version=2 rules=13 files=0 Internal requirements count=1 size=200 kdg@admins-Mac-mini /Applications % codesign -dvvv ./VirtualCamera.app Executable=/Applications/VirtualCamera.app/Contents/MacOS/VirtualCamera Identifier=com.visicom.VirtualCamera Format=app bundle with Mach-O universal (x86_64 arm64) CodeDirectory v=20500 size=1989 flags=0x10700(hard,kill,expires,runtime) hashes=51+7 location=embedded Hash type=sha256 size=32 CandidateCDHash sha256=31e15fbbd436a67a20c5b58c597d8a4796a67720 CandidateCDHashFull sha256=31e15fbbd436a67a20c5b58c597d8a4796a6772020308fb69f4ee80b4e32788b Hash choices=sha256 CMSDigest=31e15fbbd436a67a20c5b58c597d8a4796a6772020308fb69f4ee80b4e32788b CMSDigestType=2 CDHash=31e15fbbd436a67a20c5b58c597d8a4796a67720 Signature size=9006 Authority=Developer ID Application: Visicom Media Inc. (6SUWV7QQBJ) Authority=Developer ID Certification Authority Authority=Apple Root CA Timestamp=7 Jul 2022, 21:58:09 Info.plist entries=20 TeamIdentifier=6SUWV7QQBJ Runtime Version=12.3.0 Sealed Resources version=2 rules=13 files=4 Internal requirements count=1 size=188 Thanks in advance!
Posted
by kdg82.
Last updated
.
Post not yet marked as solved
0 Replies
29 Views
Hi All I am asking a solution to project my application is stolen by re-compile source or something like that. Is there any way to verify Developer certificate or Profile to make sure that the App is installed from correct Developer account? I saw that we can receive some useful information from embedded.mobileprovision. However, it looks this file does not exist when we install app from AppStore.
Posted Last updated
.
Post not yet marked as solved
1 Replies
36 Views
I just upgraded to macOS 12.5, installed XCode 13.4.1, built a .DMG installation file for my app (using Qt Creator), and proceeded to use my Apple Developer status for the first time (ta-da!) to acquire a Developer ID Installer certificate. That certificate is now visible in Keychain Access. However, it is noted as 'certificate is not trusted'. I did read that old intermediary certificates could be the cause of this but I also read that new versions of XCode automatically updates those intermediary certificates. Questions: (1) How do I check that the necessary intermediate certificates are OK? (2) Am I missing some action I need to do in XCode? So far I did nothing but launch XCode and close it again. (3) Given that I will get my certificate trusted at some point, what are the steps I should go through (in XCode or in Terminal) to codesign my .DMG file, so that it will install without warnings on another Mac computer? I have found it impossible to find instructions for this straightforward task. -- I am not going to use the App Store.
Posted Last updated
.
Post not yet marked as solved
4 Replies
330 Views
I am a developer. I have distributed apps via the Apple Store Connect. Today I wrote a fun, simple Xcode app for my friend's 2-yr-old son. The app contains family photos etc so should not be made public. I have deployed the app on my iPhone but would love to have my friend, my friend's wife, as well as the grandparents and may be a couple of friends to have the app on their different iPhones. Can anyone advise as to what is the simplest way of doing this? Thank you.
Posted
by abacaba.
Last updated
.
Post marked as solved
2 Replies
46 Views
Hi there, I'm posting this here as directed by Apple Developer Program Support over email. I was wondering if I can use a developer certificate and notary services in a macOS VM running on Apple hardware? My VMs run under QEMU/KVM on top of Linux (as I'm more familiar with the tooling and platform) on Intel Apple hardware. I'd like to confirm that using these with a developer certificate and notary services wouldn't be in breach of Apple's EULA, or be generally disliked by Apple or undesirable for any other reason. I have not joined the Developer program yet. Thanks in advance, Hamish
Posted Last updated
.
Post not yet marked as solved
1 Replies
61 Views
@eskimo Does Mac support Counter Signature and Detached Signature? If yes, then which API call from security framework is used to get those signature informations ?
Posted Last updated
.
Post not yet marked as solved
1 Replies
47 Views
I have a file that is a program "add-on" that's a single flat-file that's placed in the "Users/Shared" folder. Historically, I've been able to code-sign this file with the "Developer ID Application" certificate, then nest it in a DMG file, code-sign the DMG file with the "Developer ID Application" certificate, and then submit for notarization. The issue with this was that users had to undergo manual steps to ensure the file was placed in the correct location. I then found "Packages" (http://s.sudre.free.fr/Packaging.html) which provide a UI for creating PKG files. I added the "Developer ID Installer" to the Packages preferences for signing the PKG file during the build process. No matter the approach the file never get correctly signed and fails notarization. I have tried not signing during Packages build, and then performing the certification with Terminal. "codesign --options=runtime --sign 'Developer ID Installer: XYZ123' -v /path/to/pkg-file" When I do that I get the error: "Developer ID Installer: XYZ123: this identity cannot be used for signing code" From looking at other posts I've tried: security find-identity which returns both of the correct Certificates for Application and Installer. So it is a valid certificate, but it doesn't seem to work. I've also checked on the Apple Developer website to confirm that the certificates are valid and haven't expired. I've contacted the Packages application support over the last 3-4 days but we still can't seem to figure out what is causing it to fail. Any help would be really appreicated
Posted
by adminTC.
Last updated
.
Post not yet marked as solved
3 Replies
506 Views
Hello, My mac application update is in the development stage. For testing, I code signed my application using "Apple Development". But, the team is unable to launch the application. We get the error: "App" is damaged and can't be opened. Delete "App" and download it again from the AppStore. I am archiving the application using XCode 13(13A233) in MacOS Monterey 12.0.1 This is a new found issue after updating to Monterey as I have been able to test my app in Big Sur and below macOS versions. The certificate is valid till Dec 17th. Since I am using Push Notification service, Provisioning Profile including this certificate is being used and the team's systems have also been added. Any assistance on rectifying this issue will be very helpful and appreciated. Thank you.
Posted Last updated
.
Post not yet marked as solved
0 Replies
101 Views
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.
Posted Last updated
.
Post marked as solved
4 Replies
145 Views
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
Posted
by GNUGradyn.
Last updated
.
Post not yet marked as solved
1 Replies
83 Views
Hi Folks Wonder if someone can help or has any experience with this. Building a macOS app that calls some python scripts. This works ok. I have been trying to bundle into the app, a relocatable version of python, so python is available without having to download anything else. As soon as I add it to the Xcode project, the app will compile but I cannot sign it or notarise it. When I added the python folder, its selected to just copy to the apps resource folder. The error I get is "Found an unexpected Mach-O header code: 0xb17c0de" A bit obscure, but as Apple no longer bundle Python, I thought this could be a way to go. Thanks in advance.
Posted Last updated
.
Post not yet marked as solved
6 Replies
1.5k Views
Recently I run my project that is made on swift and for macos platform is show error releated to invalid code signature when i run my project it build successfully but while running it got crashed i am new to macos programming. I have no clue why it is happening can any one please help me out. I gave crash log of my project below. Incident Identifier: 910AC258-2D42-49BF-97A8-4BE12DCC6966 CrashReporter Key: 1227636F-8AF2-2CE1-49D8-7EDF3AC89311 Hardware Model: MacBookAir10,1 Process: PinStation [6093] Path: /Users/USER/Library/Developer/Xcode/DerivedData/PinStation-fpatihoffhnjvuevcbfrmchdzigk/Build/Products/Debug/PinStation.app/Contents/MacOS/PinStation Identifier: app.pinstation.pinstationapp Version: 1 Code Type: X86-64 (Native) Role: Default Parent Process: launchd [1] Coalition: app.pinstation.pinstationapp [1681] Date/Time: 2022-01-20 17:39:27.2638 +0530 Launch Time: 2022-01-20 17:39:26.8987 +0530 OS Version: macOS 12.0.1 (21A559) Release Type: User Report Version: 104 Exception Type: EXC_CRASH (SIGKILL (Code Signature Invalid)) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: CODESIGNING 1 Triggered by Thread: 0 Thread 0 Crashed: 0 0x7ff7ffd55a2c 0x7ff7ffd52000 + 14892 Thread 0 crashed with ARM Thread State (64-bit): x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000 x4: 0x0000000000000000 x5: 0x0000000000000000 x6: 0x0000000000000000 x7: 0x0000000000000000 x8: 0x0000000000000000 x9: 0x0000000000000000 x10: 0x0000000000000000 x11: 0x0000000000000000 x12: 0x0000000000000000 x13: 0x0000000000000000 x14: 0x0000000000000000 x15: 0x0000000000000000 x16: 0x0000000000000000 x17: 0x0000000000000000 x18: 0x0000000000000000 x19: 0x0000000000000000 x20: 0x0000000000000000 x21: 0x0000000000000000 x22: 0x0000000000000000 x23: 0x0000000000000000 x24: 0x0000000000000000 x25: 0x0000000000000000 x26: 0x0000000000000000 x27: 0x0000000000000000 x28: 0x0000000000000000 fp: 0x0000000000000000 lr: 0x0000000000000000 sp: 0x000000030523f3f0 pc: 0x00007ff7ffd55a2c cpsr: 0x00000000 far: 0x0000000000000000 esr: 0x00000000 Address size fault Binary Images: 0x7ff7ffd52000 - 0x7ff7ffd81fff (*) <9f5d65be-d8d0-3979-bb05-e651a67e785c> ??? Error Formulating Crash Report: dyld_process_snapshot_get_shared_cache failed EOF Full Report {"app_name":"PinStation","timestamp":"2022-01-20 17:39:27.00 +0530","app_version":"","slice_uuid":"4075aed2-cd46-353e-9feb-2a81fba44668","build_version":"1","platform":0,"bundleID":"app.pinstation.pinstationapp","share_with_app_devs":1,"is_first_party":0,"bug_type":"309","os_version":"macOS 12.0.1 (21A559)","incident_id":"910AC258-2D42-49BF-97A8-4BE12DCC6966","name":"PinStation"} { "uptime" : 2900, "procLaunch" : "2022-01-20 17:39:26.8987 +0530", "procRole" : "Default", "version" : 2, "userID" : 501, "deployVersion" : 210, "modelCode" : "MacBookAir10,1", "procStartAbsTime" : 70751832064, "coalitionID" : 1681, "osVersion" : { "train" : "macOS 12.0.1", "build" : "21A559", "releaseType" : "User" }, "captureTime" : "2022-01-20 17:39:27.2638 +0530", "incident" : "910AC258-2D42-49BF-97A8-4BE12DCC6966", "bug_type" : "309", "pid" : 6093, "procExitAbsTime" : 70757534356, "translated" : true, "cpuType" : "X86-64", "procName" : "PinStation", "procPath" : "/Users/USER/Library/Developer/Xcode/DerivedData/PinStation-fpatihoffhnjvuevcbfrmchdzigk/Build/Products/Debug/PinStation.app/Contents/MacOS/PinStation", "bundleInfo" : {"CFBundleVersion":"1","CFBundleIdentifier":"app.pinstation.pinstationapp"}, "storeInfo" : {"deviceIdentifierForVendor":"C8C9F935-B8DD-58EF-969E-4FFF48F19894","thirdParty":true}, "parentProc" : "launchd", "parentPid" : 1, "coalitionName" : "app.pinstation.pinstationapp", "crashReporterKey" : "1227636F-8AF2-2CE1-49D8-7EDF3AC89311", "sip" : "enabled", "isCorpse" : 1, "exception" : {"codes":"0x0000000000000000, 0x0000000000000000","rawCodes":[0,0],"type":"EXC_CRASH","signal":"SIGKILL (Code Signature Invalid)"}, "termination" : {"namespace":"CODESIGNING","flags":66,"code":1}, "extMods" : {"caller":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"system":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"targeted":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"warnings":0}, "faultingThread" : 0, "threads" : [{"triggered":true,"id":52441,"threadState":{"x":[{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0},{"value":0}],"flavor":"ARM_THREAD_STATE64","lr":{"value":0},"cpsr":{"value":0},"fp":{"value":0},"sp":{"value":12971144176},"esr":{"value":0,"description":" Address size fault"},"pc":{"value":140703125821996,"matchesCrashFrame":1},"far":{"value":0}},"frames":[{"imageOffset":14892,"imageIndex":0}]}], "usedImages" : [ { "source" : "P", "arch" : "arm64", "base" : 140703125807104, "size" : 196608, "uuid" : "9f5d65be-d8d0-3979-bb05-e651a67e785c", "name" : "" } ], "reportNotes" : [ "dyld_process_snapshot_get_shared_cache failed" ] }
Posted
by Pooja.
Last updated
.
Post marked as solved
4 Replies
134 Views
Normally, after archive, after click Distrubute App, there will be a window called "Re-sign ***". And the window will offer two selections include: "Automatically manage signing" and "Manually manage signing". But once my project contains some embed frameworks in project(first two in image 2, WebRTC related framework is managed by pods), when distribute in organizer, there will not show selection window, and go directly to Manually manage signing window. My project also contains pods to manage other code, and I do not know it is related. Is this a bug or something, hope someone can fix this, cause manually manage code sign is not a good exp.
Posted
by zaikai.
Last updated
.
Post marked as Apple Recommended
3.4k Views
We are facing following message "A timestamp was expected but was not found" during codesign for following .dylib and .pkg and it cause notarization process failed. We are facing this issue for last 3 days and we have access for timestamp.apple.com and 17.0.0.0/8 and we didn't change firewall settings. We are facing this issue randomly and not for all time(scenario is 3:1). We tried the below command to sign the package, codesign --verbose --deep --force --timestamp --options=runtime --sign "<CODE SIGN IDENTITY>" <TO BE SIGNED PACAKGE> Kindly let us know how to fix this probelm.
Posted Last updated
.
Post marked as solved
5 Replies
183 Views
Xcode version : 14.0 Beta 3 macOS version : 13 Beta 3(22A5295i) Hi, I'm signing the DriverKit in Developer ID Application type profile with Developer ID Application (With Kext) type certificate on Xcode. But status shows error with"Xcode 14 and later requires a DriverKit development profile enabled for IOS and macOS.Visit the developer website to create or download a DriverKit profile" I have downloaded all profiles and Certificates to my Mac and installed all of them, then checked the website. I'm wondering what's different between "Development type" & "Developer ID Application type" profile ? and the reason why "2022-07-22 14:41:54.162815+0800 0x22ee2    Error       0x0                  138    0    kernelmanagerd: Error occurred while handling request "DextLaunch(arguments: Optional(["Driver Extension Server Name": com.asix.dext.usbdevice, "Check In Token": 371, "Driver Extension Server Tag": 4294975444, "CFBundleIdentifier": com.asix.dext.usbdevice, "DriverKit Reslide Shared Cache": 0, "kOSBundleDextUniqueIdentifier": <222f1e51 f5e890f7 b467c2a0 da761dbd 9b14dc5f 1bf56ff6 4eeab6b2 fed9683c>]))": Error Domain=NSPOSIXErrorDomain Code=8 "Exec format error" error code show on when I starting the app. I'll appreciate that someone can give me some idea or suggestions. Thanks a lot.
Posted
by asix.
Last updated
.
Post not yet marked as solved
0 Replies
82 Views
Hi, I would like to bundle an OpenJDK runtime into my app. When uploading to the App Store, I get the following error: CFBundleIdentifier Collision - The Info.plist CFBundleIdentifier value 'net.java.openjdk.java' of 'java' is already in use by another application. When I code-sign the JRE inside of my bundle, this embedded information is not updated or deleted. What would be the proper way to remove/ change this embedded Info.plist information? It is embedded in the java binary.
Posted Last updated
.
Post not yet marked as solved
1 Replies
70 Views
Hi, I have this error when i tried automatically manage signing. It is trying to look for  com.apple.application-identifier entitlement. I downloaded my provisioning profile and took a look, it's just application-identifier, instead of com.apple.application-identifier. I am on the version of xcode 13.4.1 Is there any thing that can be done on my end to ensure the tag is correct? Thank you
Posted
by naux.
Last updated
.
Post marked as solved
1 Replies
150 Views
I am new to app development and I am trying to launch my app generated by Xcode 13.4.1 on my real device iPhone 13 Max Pro but I am getting Unable to install "MyApp". It's been days browsing resources I still could not figure this out. My Xcode project configuration looks like this: MyApp > Signing & Capabilities > Targets > MyAppName > All Signing (Debug) Automatically manage signing is checked Team is selected Bundle Identifier is set Provisioning profile is set to Xcode Managed Profile Signing Certificate: Apple Development: MyAccountName MyApp > Signing & Capabilities > Targets > MyAppNameTests > All Signing Automatically manage signing is checked Team is selected Platform: iOS Signing Certificate: Apple Development: MyAccountName Bundle Identifier: Use iOS bundle identifier Provisioning profile None Required Error Details Unable to install "MyAppName" Domain: com.apple.dt.MobileDeviceErrorDomain Code: -402620395 User Info: {   DVTErrorCreationDateKey = "2022-07-23 21:36:34 +0000";   IDERunOperationFailingWorker = IDEInstalliPhoneLauncher; } A valid provisioning profile for this executable was not found. Domain: com.apple.dt.MobileDeviceErrorDomain Code: -402620395 My app is already accepted on appstore but I am making changes to fix some issues and I want to quickly launch it through Xcode. Please help me out. Thank you
Posted Last updated
.
Post marked as solved
2 Replies
167 Views
I want to codesign our development on macOS Monterey, but I get the following error: % sudo codesign --deep -vvv --timestamp --strict --force --verify --verbose = 4 --sign "Developer ID Application: ZZZZZZZZZZ, Inc. (ZZZZZZZZZZ)" AAAAA.framework Warning: unable to build chain to self-signed root for signer "Developer ID Application: ZZZZZZZZZZ, Inc. (ZZZZZZZZZZ)" AAAAA.framework: errSecInternalComponent In subcomponent: /Users/XXXXX/AAAAA.framework/Versions/Current/Frameworks/BBBBBB.dylib If I check "Developer ID Application: ZZZZZZZZZZ, Inc. (ZZZZZZZZZZ)" in Keychain Access, It says "This certificate is valid". Download and install Apple Root Certificates and Apple Intermediate certificates from the following websites. https://www.apple.com/certificateauthority/ If I enter "apple" or "developer id cert" in the search window at the top right of the Keychain Access screen, The same certificate downloaded and installed above but with Keychain "System Roots" will be detected. Is it correct that the same certificate of "login" and "System Roots" coexist in Keychain? Attempting to delete the "System Roots" certificate results in a deletion error and cannot be deleted. -> An error occurred while deleting "(certificate name)" / UNIX [Operation not permitted] / [OK] button Why can't I codesign our development? Could you give me some advice? Thank you.
Posted Last updated
.