Signing Certificates

RSS for tag

A signing certificate is a digital identity used for code signing during the build and archive process.

Signing Certificates Documentation

Pinned Posts

Posts under Signing Certificates tag

251 Posts
Sort by:
Post not yet marked as solved
0 Replies
146 Views
Guys, do you happen to know how it is possible to upload iOS builds to App Store Connect by using Xcode Cloud and App Store Connect API Key instead of Apple ID? We want to upload iOS builds for our clients, but some of them have Individual type of accounts, so we were used to ask them for their login and pass (Apple ID) so we can log in and create all the developer certificates prior to build upload. But now we want to remove this step from the work flow by uploading builds to their accounts by using their App Store Connect API Key instead. They would connect to their account in our website, then we'll be able to handle everything from then on, hopefully?
Posted
by levon377.
Last updated
.
Post not yet marked as solved
1 Replies
2.3k Views
Seems like there's a bug with code signing in Xcode... will load package on a simulator, but not on an actual device after creating an .ipa for development testing. There should be an update to fix this error. Details as follows: Details Domain: com.apple.dt.MobileDeviceErrorDomain Code: -402620388 User Info: {     IDERunOperationFailingWorker = IDEInstalliPhoneLauncher; } -- No code signature found. Domain: com.apple.dt.MobileDeviceErrorDomain Code: -402620388 User Info: {     DVTRadarComponentKey = 261622;     MobileDeviceErrorCode = "(0xE800801C)";     "com.apple.dtdevicekit.stacktrace" = ( 0   DTDeviceKitBase                     0x0000000125237316 DTDKCreateNSErrorFromAMDErrorCode + 220 1   DTDeviceKitBase                     0x000000012527584a __90-[DTDKMobileDeviceToken installApplicationBundleAtPath:withOptions:andError:withCallback:]_block_invoke + 155 2   DVTFoundation                       0x00000001064b6ed4 DVTInvokeWithStrongOwnership + 71 3   DTDeviceKitBase                     0x0000000125275594 -[DTDKMobileDeviceToken installApplicationBundleAtPath:withOptions:andError:withCallback:] + 1420 4   IDEiOSSupportCore                   0x0000000117dedb4e __118-[DVTiOSDevice(DVTiPhoneApplicationInstallation) processAppInstallSet:appUninstallSet:installOptions:completionBlock:]_block_invoke.292 + 3508 5   DVTFoundation                       0x00000001065eac37 __DVT_CALLING_CLIENT_BLOCK__ + 7 6   DVTFoundation                       0x00000001065ec3a3 __DVTDispatchAsync_block_invoke + 931 7   libdispatch.dylib                   0x00007fff2035a623 _dispatch_call_block_and_release + 12 8   libdispatch.dylib                   0x00007fff2035b806 _dispatch_client_callout + 8 9   libdispatch.dylib                   0x00007fff203615ea _dispatch_lane_serial_drain + 606 10  libdispatch.dylib                   0x00007fff203620ad _dispatch_lane_invoke + 366 11  libdispatch.dylib                   0x00007fff2036bc0d _dispatch_workloop_worker_thread + 811 12  libsystem_pthread.dylib             0x00007fff2050245d _pthread_wqthread + 314 13  libsystem_pthread.dylib             0x00007fff2050142f start_wqthread + 15 ); } -- Analytics Event: com.apple.dt.IDERunOperationWorkerFinished : {     "device_model" = "iPhone8,4";     "device_osBuild" = "14.6 (18F72)";     "device_platform" = "com.apple.platform.iphoneos";     "launchSession_schemeCommand" = Run;     "launchSession_state" = 1;     "launchSession_targetArch" = arm64;     "operation_duration_ms" = 1948;     "operation_errorCode" = "-402620388";     "operation_errorDomain" = "com.apple.dt.MobileDeviceErrorDomain";     "operation_errorWorker" = IDEInstalliPhoneLauncher;     "operation_name" = IDEiPhoneRunOperationWorkerGroup;     "param_consoleMode" = 0;     "param_debugger_attachToExtensions" = 0;     "param_debugger_attachToXPC" = 1;     "param_debugger_type" = 5;     "param_destination_isProxy" = 0;     "param_destination_platform" = "com.apple.platform.iphoneos";     "param_diag_MainThreadChecker_stopOnIssue" = 0;     "param_diag_MallocStackLogging_enableDuringAttach" = 0;     "param_diag_MallocStackLogging_enableForXPC" = 1;     "param_diag_allowLocationSimulation" = 1;     "param_diag_gpu_frameCapture_enable" = 0;     "param_diag_gpu_shaderValidation_enable" = 0;     "param_diag_gpu_validation_enable" = 0;     "param_diag_memoryGraphOnResourceException" = 0;     "param_diag_queueDebugging_enable" = 1;     "param_diag_runtimeProfile_generate" = 0;     "param_diag_sanitizer_asan_enable" = 0;     "param_diag_sanitizer_tsan_enable" = 0;     "param_diag_sanitizer_tsan_stopOnIssue" = 0;     "param_diag_sanitizer_ubsan_stopOnIssue" = 0;     "param_diag_showNonLocalizedStrings" = 0;     "param_diag_viewDebugging_enabled" = 1;     "param_diag_viewDebugging_insertDylibOnLaunch" = 1;     "param_install_style" = 0;     "param_launcher_UID" = 2;     "param_launcher_allowDeviceSensorReplayData" = 0;     "param_launcher_kind" = 0;     "param_launcher_style" = 0;     "param_launcher_substyle" = 0;     "param_runnable_appExtensionHostRunMode" = 0;     "param_runnable_productType" = "com.apple.product-type.application";     "param_runnable_swiftVersion" = "5.5";     "param_runnable_type" = 2;     "param_testing_launchedForTesting" = 0;     "param_testing_suppressSimulatorApp" = 0;     "param_testing_usingCLI" = 0;     "sdk_canonicalName" = "iphoneos15.0";     "sdk_osVersion" = "15.0";     "sdk_variant" = iphoneos; } -- System Information macOS Version 11.6 (Build 20G165) Xcode 13.0 (19234) (Build 13A233) Timestamp: 2021-10-20T23:50:45-04:00
Posted
by LeoNTRS.
Last updated
.
Post not yet marked as solved
0 Replies
146 Views
I try to submit my app and it says select certificate and IOS App store profiles. I use the default certificate and the app store distribution profile. However, I get two errors. Profile doesn't include the selected signing certificate Profile is not an IOS App store profile. How do I fix this and what steps does it require? This is my first app and the word "struggling" is an understatement.
Posted Last updated
.
Post not yet marked as solved
4 Replies
825 Views
Ever since I got the new m1 (macOS Monterey) I cannot build my Kotlin Multiplatform app on a real device. I have tried: resigning using the new format by following the apple documentation removing/changing provisioning profiles. here are the details of the error I get: Details Unable to install "iosApp" Domain: com.apple.dt.MobileDeviceErrorDomain Code: -402620375 User Info: {     DVTErrorCreationDateKey = "2022-03-11 09:12:04 +0000";     IDERunOperationFailingWorker = IDEInstalliPhoneLauncher; } -- 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                     0x00000001215ef076 DTDKCreateNSErrorFromAMDErrorCode + 220 1   DTDeviceKitBase                     0x000000012162d6e8 __90-[DTDKMobileDeviceToken installApplicationBundleAtPath:withOptions:andError:withCallback:]_block_invoke + 155 2   DVTFoundation                       0x000000010dff3fb4 DVTInvokeWithStrongOwnership + 71 3   DTDeviceKitBase                     0x000000012162d432 -[DTDKMobileDeviceToken installApplicationBundleAtPath:withOptions:andError:withCallback:] + 1420 4   IDEiOSSupportCore                   0x00000001213509ea __118-[DVTiOSDevice(DVTiPhoneApplicationInstallation) processAppInstallSet:appUninstallSet:installOptions:completionBlock:]_block_invoke.292 + 3508 5   DVTFoundation                       0x000000010e12898b __DVT_CALLING_CLIENT_BLOCK__ + 7 6   DVTFoundation                       0x000000010e12a0f7 __DVTDispatchAsync_block_invoke + 931 7   libdispatch.dylib                   0x00007ff819bc3ad8 _dispatch_call_block_and_release + 12 8   libdispatch.dylib                   0x00007ff819bc4cc9 _dispatch_client_callout + 8 9   libdispatch.dylib                   0x00007ff819bcacee _dispatch_lane_serial_drain + 696 10  libdispatch.dylib                   0x00007ff819bcb7c8 _dispatch_lane_invoke + 366 11  libdispatch.dylib                   0x00007ff819bd57e1 _dispatch_workloop_worker_thread + 758 12  libsystem_pthread.dylib             0x00007ff819d7b074 _pthread_wqthread + 326 13  libsystem_pthread.dylib             0x00007ff819d79ffb start_wqthread + 15 ); } -- Analytics Event: com.apple.dt.IDERunOperationWorkerFinished : {     "device_model" = "iPhone10,4";     "device_osBuild" = "15.3.1 (19D52)";     "device_platform" = "com.apple.platform.iphoneos";     "launchSession_schemeCommand" = Run;     "launchSession_state" = 1;     "launchSession_targetArch" = arm64;     "operation_duration_ms" = 5282;     "operation_errorCode" = "-402620375";     "operation_errorDomain" = "com.apple.dt.MobileDeviceErrorDomain";     "operation_errorWorker" = IDEInstalliPhoneLauncher;     "operation_name" = IDEiPhoneRunOperationWorkerGroup;     "param_consoleMode" = 0;     "param_debugger_attachToExtensions" = 0;     "param_debugger_attachToXPC" = 1;     "param_debugger_type" = 5;     "param_destination_isProxy" = 0;     "param_destination_platform" = "com.apple.platform.iphoneos";     "param_diag_MainThreadChecker_stopOnIssue" = 0;     "param_diag_MallocStackLogging_enableDuringAttach" = 0;     "param_diag_MallocStackLogging_enableForXPC" = 1;     "param_diag_allowLocationSimulation" = 1;     "param_diag_gpu_frameCapture_enable" = 0;     "param_diag_gpu_shaderValidation_enable" = 0;     "param_diag_gpu_validation_enable" = 0;     "param_diag_memoryGraphOnResourceException" = 0;     "param_diag_queueDebugging_enable" = 1;     "param_diag_runtimeProfile_generate" = 0;     "param_diag_sanitizer_asan_enable" = 0;     "param_diag_sanitizer_tsan_enable" = 0;     "param_diag_sanitizer_tsan_stopOnIssue" = 0;     "param_diag_sanitizer_ubsan_stopOnIssue" = 0;     "param_diag_showNonLocalizedStrings" = 0;     "param_diag_viewDebugging_enabled" = 1;     "param_diag_viewDebugging_insertDylibOnLaunch" = 1;     "param_install_style" = 0;     "param_launcher_UID" = 2;     "param_launcher_allowDeviceSensorReplayData" = 0;     "param_launcher_kind" = 0;     "param_launcher_style" = 0;     "param_launcher_substyle" = 0;     "param_runnable_appExtensionHostRunMode" = 0;     "param_runnable_productType" = "com.apple.product-type.application";     "param_runnable_swiftVersion" = "5.5.2";     "param_runnable_type" = 2;     "param_testing_launchedForTesting" = 0;     "param_testing_suppressSimulatorApp" = 0;     "param_testing_usingCLI" = 0;     "sdk_canonicalName" = "iphoneos15.2";     "sdk_osVersion" = "15.2";     "sdk_variant" = iphoneos; } -- System Information macOS Version 12.2.1 (Build 21D62) Xcode 13.2.1 (19586) (Build 13C100) Timestamp: 2022-03-11T11:12:04+02:00 this is the code sign of the app : Executable=/Users/yammine/Library/Developer/Xcode/DerivedData/Belight.tv-cjjqumcursyzwgexwmngzqpjxuhd/Build/Products/Debug-iphoneos/iosApp.app/iosApp Identifier=belight.tv.mobile Format=app bundle with Mach-O thin (arm64) CodeDirectory v=20400 size=173557 flags=0x0(none) hashes=5413+7 location=embedded VersionPlatform=2 VersionMin=983552 VersionSDK=983552 Hash type=sha256 size=32 CandidateCDHash sha256=ae1b67b0146f3cd850f8b50c811a30b0074e459c CandidateCDHashFull sha256=ae1b67b0146f3cd850f8b50c811a30b0074e459ccf67664a03c126325513e08e Hash choices=sha256 CMSDigest=ae1b67b0146f3cd850f8b50c811a30b0074e459ccf67664a03c126325513e08e CMSDigestType=2 Executable Segment base=0 Executable Segment limit=9486336 Executable Segment flags=0x11 Page size=4096 -7=b82416cc7a192ddfb0e55772ad1c5665dc56603b7270c27f276b7386ff210d24 -6=0000000000000000000000000000000000000000000000000000000000000000 -5=ecd453cfb0a1a40dee167d7ba4c8eb6f63853a2a337425a64656515b582c3158 -4=0000000000000000000000000000000000000000000000000000000000000000 -3=570369fde135209c46f351df9690b3e76fe1d9733f8c8ea342f367dbf9a097ec -2=0fb4a4176ef550d3bbaa6681c6282857e2554ba65de2f68af504028fa7e0322e CDHash=ae1b67b0146f3cd850f8b50c811a30b0074e459c Signature size=4797 Authority=Apple Development: yammine@tomorrow.services (3DPU6CX8ZZ) Authority=Apple Worldwide Developer Relations Certification Authority Authority=Apple Root CA Signed Time=Mar 11, 2022 at 11:11:54 AM Info.plist entries=31 TeamIdentifier=5BSNGUTQ53 Sealed Resources version=2 rules=10 files=20 Internal requirements count=1 size=196
Posted Last updated
.
Post not yet marked as solved
1 Replies
129 Views
I recently bought a class 3 Digital signature using Epass2003 token and was able to install the drivers and certificates. the application EnterMagSf was even recognising the token, however, at the time of signing, the application crashes, Tried multiple times, but the signing application crashes just at the time of signing.
Posted Last updated
.
Post not yet marked as solved
7 Replies
14k Views
Creating a new Admin account or the existing accounts have the option for access to certificates, Identifiers and Profile disabled. I checked it Admin and Account Holder account. Our Apple developer account is paid. Can I know why do I see this issue?Thanks in advance
Posted Last updated
.
Post not yet marked as solved
0 Replies
131 Views
I thought some folks on this forum might find it useful, so I'm sharing that I've just open sourced a Swift package called Required which parses and evaluates requirements written in Apple's Code Signing Requirement Language. Amongst other uses, this package can be quite useful in debugging security requirements used to secure XPC communications. This package only uses public APIs and supports OS X 10.10 and later. (The parser itself has no platform dependencies at all and could in theory be run on any platform Swift supports.) As an example of how the package works, to see whether and how an application satisfies its designated requirement: // Retrieve the designated requirement for Numbers let url = URL(fileURLWithPath: "/Applications/Numbers.app") var code: SecStaticCode? SecStaticCodeCreateWithPath(url as CFURL, [], &code) var requirement: SecRequirement? SecCodeCopyDesignatedRequirement(code!, [], &requirement) // See whether and how Numbers satisifies its designated requirement let abstractRequirement = try Parser.parse(requirement: requirement!) let evaluation = try abstractRequirement.evaluateForStaticCode(code!) print("Does \(url.lastPathComponent) satisfy its designated requirement?") print(evaluation.isSatisfied ? "Yes" : "No") print("\nEvaluation tree:") print(evaluation.prettyDescription) Which outputs: Does Numbers.app satisfy its designated requirement? Yes Evaluation tree: and {true} |--() {true} | \--or {true} | |--and {true} | | |--anchor apple generic {true} | | \--certificate leaf[field.1.2.840.113635.100.6.1.9] {true} | \--and {false} | |--and {false} | | |--and {false} | | | |--anchor apple generic {true} | | | \--certificate 1[field.1.2.840.113635.100.6.2.6] {false}¹ | | \--certificate leaf[field.1.2.840.113635.100.6.1.13] {false}² | \--certificate leaf[subject.OU] = K36BKF7T3D {false}³ \--identifier "com.apple.iWork.Numbers" {true} Constraints not satisfied: 1. The certificate <Apple Worldwide Developer Relations Certification Authority> does not contain OID 1.2.840.113635.100.6.2.6 2. The certificate <Apple Mac OS Application Signing> does not contain OID 1.2.840.113635.100.6.1.13 3. The certificate <Apple Mac OS Application Signing> does not contain element subject.OU
Posted
by jkaplan.
Last updated
.
Post marked as solved
3 Replies
229 Views
Hello, I'm planning to switch to a new macbook soon. I currently use XCode to develop and publish Apps. I currently have 2 certificates a "Development" one and "Distribution Managed" one. I use XCode to generate identifiers and sign apps for me automatically. Do I have to backup anything before switching to the new Macbook? Will I be able to keep updating and publishing my apps just by logging in XCode? Thank you.
Posted Last updated
.
Post not yet marked as solved
1 Replies
170 Views
I am a member of a development team that recently renewed our Apple Development certificate. The admin on our team created the certificate, and I downloaded the .p12 file to my Mac and was able to open it in Keychain. But when I try to update my certificates in Xcode &gt; Preferences &gt; Accounts &gt; Manage Certificates &gt; + &gt; Apple Development, it shows the message, There is a problem with the request entity. You already have a current Development certificate or a pending certificate request. In the Manage Certificates window, there are 2 Apple Development certificates shown. They are both named [MyName]'s Mac mini, and they are both greyed out. The Creator is listed as my account, and the Status is listed as "Not in Keychain". If I right-click on the certificates, they only have the option to Email Creator. The admin confirmed that there is no certificate called [MyName]'s Mac mini on the apple developer website. My account does not have access to the certificates section, so I can't check whether there is one associated with my account. I have already tried the following Sign out of Accounts in Xcode, quit Xcode, and then sign back in Delete the certificate and re-import it to Keychain Restart computer I am using Xcode 13.3 and macOS Monterey Version 12.3.1 As a result, I am unable to build our project to a physical device. How do I remove/update the current Development certificate so that I can add the latest certificate to my Mac?
Posted Last updated
.
Post not yet marked as solved
3 Replies
538 Views
Hi allHow's it going?I am completely new in ios development.Would be nice if i could find anwsers from the forum.I did a very brief app, just a label with my name.And I want to upload it to Testflight.So I select Generic ios device and went to Product &gt; ArchiveAnd then it asked for Keychain Access. Where exactly I can find the correct KeyChain Access?Many Thanks
Posted Last updated
.
Post not yet marked as solved
4 Replies
2.2k Views
PresentationI've an Apple Dev ID as a member of an organisation.I use Visual Studio 2019 on Windows 10 to build the ipa file via the Mac using Xcode version 11.2.1.The ipa file is uploaded to the store using Fastlane by the administrator of the same organisation.DESCRIPTION OF PROBLEMWe've this problem when uploading ipa file on the store.With the developer provisioning profile, I can execute my app without problem.But with the distribution provisionning profile created by the administrators, when they upload the ipa file,we have the errors above. The distribution provisionning profile is generated by them with the iCloud option Include Cloudkit support (requires Xcode 6).As a member, I download the profile on the Mac and double-click on it to load it in Xcode.In order to see the profile in question in Visual Studio 2019, I download the profile from Xcode and build the ipa file with theconfiguration Ad-Hoc, the only one that I can use with the profile provided.In the Entilements file, I only have these two lines :1)&lt;key&gt;com.apple.developer.icloud-container-environment&lt;/key&gt;&lt;string&gt;Production&lt;/string&gt;.Or with all these features declared in Entitlements file :2)&lt;key&gt;com.apple.developer.icloud-container-identifiers&lt;/key&gt;&lt;array&gt;&lt;string&gt;iCloud.com.[mycompnay].[myapp]&lt;/string&gt;&lt;/array&gt;&lt;key&gt;com.apple.developer.ubiquity-kvstore-identifier&lt;/key&gt;&lt;string&gt;$(AppIdentifierPrefix)$(CFBundleIdentifier)&lt;/string&gt;&lt;key&gt;com.apple.developer.icloud-services&lt;/key&gt;&lt;array&gt;&lt;string&gt;CloudDocuments&lt;/string&gt;&lt;string&gt;CloudKit&lt;/string&gt;&lt;/array&gt;When uploading the ipa file, we always have the same errors having 1) or 2) in the Entitlements file:ERROR ITMS-90045: "Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'com.apple.developer.icloud-container-development-container-identifiers' in 'Payload/MyCompnayMyApp.app/MyCompnayMyApp' is not supported."ERROR ITMS-90046: "Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, value '*' for key 'com.apple.developer.icloud-services' in 'Payload/MyCompnayMyApp.app/MyCompnayMyApp' is not supported."ERROR ITMS-90046: "Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, value 'Development' for key 'com.apple.developer.icloud-container-environment' in 'Payload/MyCompnayMyApp.app/MyCompnayMyApp' is not supported."ERROR ITMS-90211: "Invalid Code Signing Entitlements. The signature for your app bundle contains entitlement values that are not supported. For the com.apple.developer.ubiquity-kvstore-identifier entitlement, the value must start with the prefix provided by Apple in the provisioning profile, followed by characters that are uppercase or lowercase Roman letters [A-Z, a-z], the digits 0 through 9, dot ['.'], or hyphen ['-'], and not contain any wildcard characters. Specifically, value 'AN8YKZK4DA.*' for the key 'com.apple.developer.ubiquity-kvstore-identifier' in 'Payload/MyCompnayMyApp.app/MyCompnayMyApp' is not supported."ERROR ITMS-90045: "Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'com.apple.developer.icloud-container-development-container-identifiers' in 'Payload/MyCompnayMyApp.app/MyCompnayMyApp' is not supported."ERROR ITMS-90046: "Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, value '*' for key 'com.apple.developer.icloud-services' in 'Payload/MyCompnayMyApp.app/MyCompnayMyApp' is not supported."ERROR ITMS-90046: "Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, value 'Development' for key 'com.apple.developer.icloud-container-environment' in 'Payload/MyCompnayMyApp.app/MyCompnayMyApp' is not supported."ERROR ITMS-90211: "Invalid Code Signing Entitlements. The signature for your app bundle contains entitlement values that are not supported. For the com.apple.developer.ubiquity-kvstore-identifier entitlement, the value must start with the prefix provided by Apple in the provisioning profile, followed by characters that are uppercase or lowercase Roman letters [A-Z, a-z], the digits 0 through 9, dot ['.'], or hyphen ['-'], and not contain any wildcard characters. Specifically, value 'AN8YKZK4DA.*' for the key 'com.apple.developer.ubiquity-kvstore-identifier' in 'Payload/MyCompnayMyApp.app/MyCompnayMyApp' is not supported."Questions:What did we do wrong?Can a member of an organisation build an ipa file via Xcode which will be uploaded by an administrator of the same organisation using Fastlane?STEPS TO REPRODUCE Each time, the ipa file is uploaded with Fastlane.
Posted
by jplee.
Last updated
.
Post not yet marked as solved
0 Replies
130 Views
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. 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 Entitlements documentation Don’t Run App Store Distribution-Signed Code DevForums post Mac code signing: DevForums tag: Developer ID Creating Distribution-Signed Code for Mac DevForums post Packaging Mac Software for Distribution DevForums post Manual Code Signing Example DevForums post 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 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"
Posted
by eskimo.
Last updated
.
Post not yet marked as solved
1 Replies
240 Views
I have an application for macOS that uses core data to save data. I switched to CloudKit so I can sync that data with its iOS counterpart. This is on Xcode 13.4. Even since I did that I get the error: When I try to submit it for a distribution with "Developer ID" I have been going in circles for the last two days. I have tried all the stuff several articles here at SO mentioned (e.g. this one), or the Apple Dev Forums (for example this one). I have tried deleting certs, regenerating them, adding them again, downloading "manual profiles" again, going to the building settings and changing certs and options... It doesn't matter. It goes nowhere. Here's the thing, if I go back to the version without iCloud, all is good. Same with any iOS app that uses iCloud. All builds, and all goes to Apple without any issues. It's only this app. For the sake of testing I created a new macOS app, and from the get go I enabled CloudKit. Same error. So, what's missing? Is there any special foo or incantation I need to utter to get an macOS app to use iCloud and be able to be distributed? Thanks
Posted Last updated
.
Post not yet marked as solved
2 Replies
4k Views
EDIT: I received an email back from Apple on this issue and they verified that if In-App Purchase is enabled, it will not affect our fee waiver. They only check to make sure that there are no in-app purchases available within the app. I'm choosing not to delete this question in case someone else encounters this.Preface: I work for a college, and our Developer account had the fee waived. One of the conditions of the waiver is that all apps deployed under the account must be free of charge. I have asked Apple that if our app has In-App Purchase enabled, if it will violate the waiver's conditions, and I was told that yes, it would.When I created an App ID for our app, In-App Purchase was enabled. I have googled several different ways on how to disable in-app purchases but I haven't found anything that works.https://stackoverflow.com/questions/15913115/ios-how-can-i-deselect-game-center-and-in-app-purchase-when-i-try-to-register-myCreating new App ID, selected the wildcard radio button, then selecting explicit... In-App Purchase was re-enabled as soon as I re-selected explicit.Adding/removing In-App Purchase from XcodeAttempting to fool the configuration by unchecking the checkbox through Javascript.Apple has sent me the in-app purchases best practices documentation, but there is no statement on how to remove/disable in-app purchases, only how to use the framework. For what it's worth, the StoreKit framework is not included on the project.I've found some solutions that require the app to already be published through iTunes Connect, which I have not done yet. I'm afraid that if I submit the app for review, Apple will flag the app and our account because In-App Purchase is enabled. I do not want to do or try anything that has even the slightest chance of jeopardizing our fee waiver.I want to use the explicit bundle app ID because I am planning to deploy the test version of the app through Testflight.Is there another way to disable In-App Purchase from the app ID? Is my fear of our waiver being revoked if I try publishing the app for review in iTunes Connect misplaced?
Posted Last updated
.
Post not yet marked as solved
6 Replies
2.7k Views
I'm trying to migrate the scripts that build my application from an Intel Mac running Mojave (Xcode 10.3) to an M1 Mac running Big Sur (Xcode 12.5.1). On the M1 Mac, codesign triggers a pop up a window asking for an admin username/password each time it signs something. This happens whether it is invoked via a script or directly in Terminal. The pop-up appears twice when signing a Universal binary, once when signing a single-architecture binary. The popup says: macOS wants to make changes. Enter an adminstrator's name and password to allow this. macOS wants to use the "System" keychain. and it has a "Deny" button and an "Allow" button, but not an "Always Allow" button. (Another issue: the username is not pre-populated, even though I am logged in as an admin.) My "Developer ID Application" certificate is stored in my login keychain, as is the "Apple Worldwide Developer Relations Certification Authority" certificate, which expires 2030-02-19. The "System" keychain contains an "Apple Application Integration Certification Authority" certificate expiring 2026-10-20. (Another issue: that certificate can't be deleted!) Suggestions?
Posted
by jkbull.
Last updated
.
Post not yet marked as solved
1 Replies
222 Views
I have an iOS app that isn't acceptable for the App Store (it is used to open the front door of my apartment building so not of general interest). I can install it on my iPhone from Xcode easily enough but after a week it becomes "no longer available". I assume this is because the signature expires. I created a new code signing certificate using Keychain Access that lasts much longer. I then found the archive of my app that Xcode produced, removed the signature and resigned it with my new certificate: codesign --remove-signature -v Products/Applications/FrontDoor.app codesign -s "My Self Signed Code Signing Cert" -v Products/Applications/FrontDoor.app Now I am stuck trying to work out how to load the archive onto my (and hopefully my partner's) iPhone(s). Am I on the right track or is there a better way to handle this? Is it possible to load an archive onto an iPhone connected via USB?
Posted
by cqexbesd.
Last updated
.
Post not yet marked as solved
4 Replies
548 Views
Hi, I'm using fastlane to build/sign my project and it works perfectly when I ran it in my Mac. I'm trying to setup some Jenkins CI/CD server in AWS EC2, and I started to have a problem with code sign. I realized that it's not something related to AWS, because if I ssh to my own Mac using "ssh localhost" it's possible to simulate the problem. To isolate the problem, I'm using this very simple project with fastlane: https://github.com/rlechetaudemy/helloios This issue is also not related with match, because if you setup fastlane with manual signing, it returns the same error. I also tried to use the 'setup_ci' action before build/sign but without success. setup_ci( force: true ) These are the logs: [13:11:36]: ▸ Copying GoogleService-Info.plist [13:11:37]: ▸ Processing Info.plist [13:11:38]: ▸ ** ARCHIVE FAILED ** [13:11:38]: ▸ The following build commands failed: [13:11:38]: ▸ CodeSign /Users/user/Library/Developer/Xcode/DerivedData/HelloIOS-eibmqfokwytdeddxnnluvsuzbtlp/Build/Intermediates.noindex/ArchiveIntermediates/HelloIOS\ (iOS)/InstallationBuildProductsLocation/Applications/HelloIOS.app (in target 'HelloIOS (iOS)' from project 'HelloIOS') [13:11:38]: ▸ (1 failure) ▸ Processing Pods-HelloIOS (iOS)-Info.plist ▸ Processing Info.plist ** ARCHIVE FAILED ** The following build commands failed: CodeSign /Users/user/Library/Developer/Xcode/DerivedData/HelloIOS-eibmqfokwytdeddxnnluvsuzbtlp/Build/Intermediates.noindex/ArchiveIntermediates/HelloIOS\ (iOS)/InstallationBuildProductsLocation/Applications/HelloIOS.app (in target 'HelloIOS (iOS)' from project 'HelloIOS') (1 failure) [13:11:38]: Exit status: 65 +---------------+-------------------------+ |      Build environment      | +---------------+-------------------------+ | xcode_path  | /Applications/Xcode.app | | gym_version  | 2.205.2         | | export_method | ad-hoc         | | sdk      | iPhoneOS15.2.sdk    | +---------------+-------------------------+ [13:11:38]: ▸              (ef0fada7-88c4-413f-a9e5-7d875f07e324) [13:11:38]: ▸     [13:11:38]: ▸   /usr/bin/codesign --force --sign CB4DB01189506EF6F172982414A36378AE18F48F --entitlements /Users/user/Library/Developer/Xcode/DerivedData/HelloIOS-eibmqfokwytdeddxnnluvsuzbtlp/Build/Intermediates.noindex/ArchiveIntermediates/HelloIOS\ (iOS)/IntermediateBuildFilesPath/HelloIOS.build/AdHoc-iphoneos/HelloIOS\ (iOS).build/HelloIOS.app.xcent --generate-entitlement-der /Users/user/Library/Developer/Xcode/DerivedData/HelloIOS-eibmqfokwytdeddxnnluvsuzbtlp/Build/Intermediates.noindex/ArchiveIntermediates/HelloIOS\ (iOS)/InstallationBuildProductsLocation/Applications/HelloIOS.app [13:11:38]: ▸ /Users/user/Library/Developer/Xcode/DerivedData/HelloIOS-eibmqfokwytdeddxnnluvsuzbtlp/Build/Intermediates.noindex/ArchiveIntermediates/HelloIOS (iOS)/InstallationBuildProductsLocation/Applications/HelloIOS.app: errSecInternalComponent [13:11:38]: ▸ Command CodeSign failed with a nonzero exit code [13:11:38]:  [13:11:38]: ⬆️ Check out the few lines of raw xcodebuild output above for potential hints on how to solve this error [13:11:38]: 📋 For the complete and more detailed error log, check the full log at: [13:11:38]: 📋 /Users/user/Library/Logs/gym/HelloIOS-HelloIOS (iOS).log [13:11:38]:  [13:11:38]: Looks like fastlane ran into a build/archive error with your project [13:11:38]: It's hard to tell what's causing the error, so we wrote some guides on how [13:11:38]: to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/ [13:11:38]: Before submitting an issue on GitHub, please follow the guide above and make [13:11:38]: sure your project is set up correctly. [13:11:38]: fastlane uses xcodebuild commands to generate your binary, you can see the [13:11:38]: the full commands printed out in yellow in the above log. [13:11:38]: Make sure to inspect the output above, as usually you'll find more error information there [13:11:38]:  +---------------------------+----------------------------------------------------------+ |                   Lane Context                   | +---------------------------+----------------------------------------------------------+ | DEFAULT_PLATFORM     | ios                           | | PLATFORM_NAME       | ios                           | | LANE_NAME         | ios firebase                       | | KEYCHAIN_PATH       | ~/Library/Keychains/fastlane_tmp_keychain        | | ORIGINAL_DEFAULT_KEYCHAIN | "/Users/user/Library/Keychains/fastlane_tmp_keychain-db" | +---------------------------+----------------------------------------------------------+ [13:11:38]: Error building the application - see the log above +------+-------------------------------+-------------+ |         fastlane summary         | +------+-------------------------------+-------------+ | Step | Action            | Time (in s) | +------+-------------------------------+-------------+ | 1  | Verifying fastlane version  | 0      | | 2  | default_platform       | 0      | | 3  | Switch to ios buildAdHoc lane | 0      | | 4  | setup_ci           | 0      | | 5  | cocoapods           | 4      | | 💥  | build_app           | 36     | +------+-------------------------------+-------------+
Posted
by rlecheta.
Last updated
.
Post marked as solved
2 Replies
272 Views
I have been working on signing an app from a developer for our own purpose of publishing it to our intune company portal. The older version of the app I can sign and publish without issue. We do have an enterprise dev account, and all they provide us is the source code. The original version does not use Push notifications, nor does it show to have any framework subfolders. That one I sign by this script I've modified over time, ( security cms -D -i [mobilprovisionfilenamefromentdevsite].mobileprovision > provision.plist /usr/libexec/PlistBuddy -x -c 'Print :Entitlements' provision.plist > entitlements.plist unzip -qq [appname]22_5_1.ipa rm -rf Payload/[appname].app/_CodeSignature/ cp [mobilprovisionfilenamefromentdevsite].mobileprovision Payload/[appname].app/embedded.mobileprovision /usr/bin/codesign --force --deep --verify --sign "[Our Certificate name redacted]" -i [the app identity name from the identity creation] --entitlements entitlements.plist Payload/[appname].app/Frameworks/* codesign -dvv Payload/[appname].app/ zip -qr [appname]22_5_1-resigned.ipa Payload/ #Copy the support files for backup mkdir [appname]22_5_1-resigned-support mv entitlements.plist [appname]22_5_1-resigned-support mv Payload [appname]22_5_1-resigned-support mv provision.plist [appname]22_5_1-resigned-support ) This works fine for the old version without Frameworks or Push Notifications The New One I have just added two lines to the script to sign the FrameWorks. rm -rf Payload/[appname].app/Frameworks/*/_CodeSignature/ /usr/bin/codesign --force --deep --verify --sign "[Our Certificate name redacted]" -i [the app identity name from the identity creation] --entitlements entitlements.plist Payload/[appname].app/Frameworks/* When I try it with or without signing the FrameWorks I am unable to get the app to function. It will load on the IPhones then just give error of "Install Pending" or "Install Failed" (0x87D13B64) We do not have access to the source code, so I cannot put it into XCode to sign it. I did recreate the mobile provisioning profile with APN and created a Cert to attach to it. I'm not sure if I need to add that certificate somewhere else or if I'm signing something wrong, but this new version is kicking my ****..
Posted Last updated
.
Post not yet marked as solved
2 Replies
1.7k Views
Hi, my Xcode 13.1 somehow not able to include my signing certificate. The error message for the distribution profile is: Provisioning profile "distribution profile name" doesn't include signing certificate "development certificate name" I have tried to remove my development certificate from my Keychain to see if it able to include the distribution certificate that has been downloaded from apple developer account and imported to my Keychain Access, but error shows: No signing certificate "iOS Development" found. Then I tried to re-add back my development certificate. However, the issues still persist. Is it because in the provisioning profile I need to tick the support Xcode 11 and above only it be able to include the certificate? Or is there any thing that I have missed out? Help would be greatly appreciated!
Posted
by hafizah.
Last updated
.