I am trying to compile an update to one of my existing apps, but I keep getting this error:Check dependenciesProvisioning profile "iOS Team Provisioning Profile: ***.xxxxx.***" doesn't include signing certificate "iPhone Developer: my name (xx43U4KZxx)".Code signing is required for product type 'Application' in SDK 'iOS 10.0'I checked my certificates here on developer.apple.com, and I have both a valid dev. cert & dist. cert.The dev cert. I created a few days ago (the old one had expired).I then downloaded it to my MAC and dbl-clicked on it.Also, I tried Xcode/Preferences->Accounts/"View Details"/"Download All"Neither seems to have worked.Is there anything else I need to do?Also, the provisioning profile for the specific app is still valid.Any help would be much appreciated!

Hi, I'm using appium to run some automated testing using an iPhone. When I launch my script a WebDriverAgent is installed on the phone. All is well when the phone is connected to internet as it can get the signatures, however when it isn't, that fails. To combat that I created a provisioning profile with 7 days offline support. My Xcode is set to Automatically Setup signing and so when I go to see what provisioning profiles it has, it is not the offline one. If I disable Auto and go in and manually download the offline provisioning profile I created, then is all working perfectly fine. I guess my question is: Can I get Xcode to automatically take the provisioning file I created rather than letting it take it's own? Cheers, Alecs B

Hi,my apps run on the iOSSimulator without problems and used to run on devices as well, but after updating to latest XCode-Version I am getting the above error message when trying to run an app on my iPhone 7. It says :"codesign wants to access key "access" in your bunch of keys . To allow this enter your password".... but my apple-Developer-ID-Password doesn't work. And until updating to latest XCode-Version I never had any problems with codesign when running an app on iPhone device.Any hints what's going wrong ?XCode Version 9.1 (9B55)iOS Version 11.1.2 (15B202)Latest High Sierra Version, macbook Pro 2015

Hey I need some... direction here. I have 2 developer "ids". Apple Development : ***@*** (ID) Apple Distribution : Company *** (ID) Now I can notarize my software using Apple Development, but I cant using Apple Distribution as it says "message": "The binary is not signed with a valid Developer ID certificate.",. What should I do to make this thing... ship-able & release-able? I'm using CMAKE, Clion, no xcode to do it automatically sadly... Can some1 hint me what ID should I use for public release? Regards Dariusz

Hello, I am trying to distribute a macOS app directly to consumers. Recently I came across this article titled 'Cloud-managed certificates', which details that Apple will sign apps by authorizing you via you Developer program membership, but would like to see if this is usable from the command line or thirdparty tools. To confirm that this article does what it says, I created a new generic SwiftUI app on a new Mac that does not have any existing "Developer ID Application" certificates in keychain. In the signing tab, it shows With this, when I 'archive', the Xcode Organizer appears. If I click distribute, then 'Developer ID', 'Upload', 'Automatically manage signing', it correctly displays "Certificate: Cloud Managed Developer ID Application" and then gives me the option to notarize it. Now, this was all done via the Xcode Organizer via an Xcode-managed app. I was wondering if it would be possible to use this cloud-managed signing service from the CLI, so that I can integrate it with existing tooling and CI/CD pipelines.

Hello, 3 months ego we started the procedure to create our own iOS MDM solution. https://developer.apple.com/business/documentation/MDM-Protocol-Reference.pdf First, we created an Apple developer account and asked to add the MDM CSR request option: our request for has been rejected. Support told us that only Apple Developer Enterprise owners can have this option. Second, The support told us to create an Apple Business Manager account: there are no option to create an MDM CSR request. Third, we asked 3 times Apple Developer Enterprise account but our requests was rejected and support asked as to create Apple Developer and Apple Business Manager accounts (already created). Someone had the same issue ? thanks ! Regards,

Background We are using a Developer ID application certificate to sign our application. We lost the private key and we need to revoke it before we can receive a new one. Per documentation (https://developer.apple.com/support/certificates/), I know that previously installed applications will still be able to run, but new installations will not be able to work. I want to confirm what will happen when we revoke the certificate so we know how to prepare customers for this upcoming change. Questions Will existing installations of the application receive a notice that the certificate has been revoked? Will previously installed applications be able to launch again after they are closed? What will the user see when they try to install the application with the revoked certificate?

I need a solid answer for my case. My company has an Enterprise account and we have already used it to publish some apps to our clients. The account has been renewed for another year. Activation Date: February 2, 2023 Expiration Date: February 2, 2024 My question, is there any action that should be taken like uploading a new version of the app before this date or even after this date ? Please note that the certification(used to signed the app) expires in next October 2023. The case if very critical and we don't want the app to be stopped suddenly.

Apple confirmed that MDM capability has been granted. But I can NOT see any changes in the "Certificates, Identifiers & Profiles" page. There are no options to create MDM Certificate: What should I do next ? Do I get the wrong entry to create MDM Certificate? Or do I need to ask Apple to add the MDM options?

I spend days figuring out the proper steps to make it work. Can anyone give hints? Using xcode's Manage Certificate I'm creating a Mac Installer Distribution certificate but while I run the command security find-identity -p codesigning -v I see nothing. However, if I create any other certificate I can see it using that command. Due to the problem with cert generation I receive an error in Transporter : The product archive package's signature is invalid. Ensure that it is signed with your "3rd Party Mac Developer Installer" certificate I already deleted all and recreated it using xcode, and also created using https://developer.apple.com/account/resources/certificates/list and downloaded it. What should I do?

I get this error when loading kext. "Authenticating extension failed: Bad code signature." The MacBook system status is as follows. There are a few points to illustrate. This kext file works fine with SIP turned off in MacBook 2018 (MacOS 10.14.6). This kext will not be released, it will only be used for debugging within our own group. This kext has been compiled into the arm64 version. The SIP option has been turned off in recovery mode and the option to reduce security has been checked for kext testing. I want to use this kext (and not distribute) if I have to use the Apple Developer program for authentication and signing and authentication. What should I do if I don't need to? Or is it not caused by certified signatures?

After not happening to me for a few months, this issue has started hitting me again with currently %100 reproducability. If turn on VPN on my Mac then instantly the developer certificates within the keychain become untrusted. But that's not all, if VPN is then turned off the certificates do not revert to their trusted status but remain untrusted. The consequence of this is that if VPN is turned on and then a build is perform, it fails, and the only way to fix things is to delete the cert(s) from they keychain and re-install them. As a remote worker, having this happen several or even dozens of times a day is incredibly annoying and frustrating. This issue has been occurring for literally years, sometimes it occurs very often, others while its quiet for a while, and has spanned multiple versions of Xcode and Mac OS. So whatever the cause is its endemic. It doesn't just affect myself, but all the members in my development team. I'm currently using Xcode 14.1 RC 2 and Monterey but I've seen this issue occur with many versions of Xcode and Mac. (I'm using Cisco AnyConnect Secure Mobility Client). If the VPN is somehow interfering/affecting the connectivity aspect when an attempt is made by Xcode to validate the certificate, then why does it not rectify itself after turning off VPN? This is so so so so annoying. Can somebody please comment on why this happens and if there's a way to prevent it.

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?

I built a Flutter app and I am trying to archive a build so I can put it on TestFlight and have some people test it on beta. However, when I archive the build, it fails with this error: Failed to create provisioning profile. There are no devices registered in your account on the developer website. Select a device run destination to have Xcode register it. and also: No profiles for '***' were found. Xcode couldn't find any iOS App Development provisioning profiles matching '***'. I set the build devices to Any iOS Device so that it can be used on all devices. How can I fix this?

I'm trying to sign and export my macOS app. I do: Archive Distribute App Developer ID -> Export -> Automatically Manage Signing -> FAIL Communication with Apple failed You are not allowed to perform this operation. Please check with one of your Team Admins, or, if you need further assistance, please contact Apple Developer Program Support. https://developer.apple.com/support No profiles for '' were found Xcode couldn't find any Developer ID provisioning profiles matching ''. It should create those for me. I tried to create them via the website, but that ends up making me create a certificate (although it is not clear what kind of certificate). So I do my best to choose the right kind, and then it still doesn't create a profile. I try again, and it says there's no certificate available, so it prompts me to do that again. WHY IS THIS STUFF STILL SO HARD TO DO?

Hi, I have this error: Provisioning profile "iOS Team Provisioning Profile: com.Mcrich23.Pickt" doesn't include the com.apple.runningboard.assertions.webkit entitlement However, I can't add this entitlement because it pretty much does not exist. Any ideas?

My company produces custom iOS applications for other businesses. One of our applications is still using iOS SDK 12 and is built using Xcode 10.3. Our normal method for distributing this app is to send clients an IPA that they re-sign with their Enterprise provisioning profile and host on their MDM for internal consumption. One client recently lost access to their Enterprise account. They need to use this app right away with less than 100 users in their team. I've generated a provisioning profile with all the UDIDs that they intend to have. I've locally re-signed the ipa on the command line with the provisioning profile, and the output of ipa info myapp.ipa shows me the correct cert, and the list of UDIDs from the profile. However, when I drag the IPA to an iPad that is on that list of UDIDs, I get the dreaded "app integrity cannot be verified" error when I try to run it. Is there any tool that can help me troubleshoot?

How can I restore a certificate?

Cannot add a iOS Distribution Certificate to my Project or Target? During the Submission for Review process, it states I should choose a Build (for Distribution) and I need to do the above add before I can do that. Here is a screen shot of my Certificates set in my Developer Account: Here is the screen shot when I double-click on the iOS Distribution Certificate above: Here is a screen shot of that Certificate in the Finder: Yet in spite of all the above evidence, here is a screen shot of my Target for both my iOS and tvOS Project: So, please provide some hints because this is the only step left before I finally submit my App to the App store.