I understand from the Xcode release notes that it is now possible to submit visionOS apps to TestFlight. I'm getting the error "Asset validation failed" "Invalid Provisioning Profile. This provisioning profile is not compatible with visionOS apps". when uploading to TestFlight. I use an Xcode managed profile, and am using the same bundle id as for the iOS and Mac versions of the app. In the "Certificates, Identifiers & Profiles" -> "Edit your App ID Configuration" it lists "iOS, iPadOS, macOS, tvOS, watchOS, visionOS" under "Platform". Is there some guidance on submitting visionOS apps to TestFlight? Any ideas on how to regenerate the profile to include visionOS apps? Thanks, Damian

Hi, I was about to delete the expired provisioning profiles, meaning the ones where it said "Expired" in the last column. Now I see there are some more where the expiration date is clearly in the past, but they don't show as expired. Any idea why that is? Kind regards Thomas

Failed to build iOS app Error (Xcode): No profiles for 'com.jurabek7788.sos' were found: Xcode couldn't find any iOS App Development provisioning profiles matching 'com.jurabek7788.sos'. Automatic signing is disabled and unable to generate a profile. To enable automatic signing, pass -allowProvisioningUpdates to xcodebuild. /Users/user/Desktop/SOS%20flutter%20/set_of_service_app/ios/Runner.xcodeproj It appears that there was a problem signing your application prior to installation on the device. Verify that the Bundle Identifier in your project is your signing id in Xcode open ios/Runner.xcworkspace Also try selecting 'Product > Build' to fix the problem. Encountered error while building for device. this is my error coming when i build ios app. And main problem is already did all the things

If I turn on (my company supplied VPN access) and then attempt to build with Xcode then that has the consequence that all the dev/distribution certificates in the keychain turn red and say "certificate is not trusted". Turning off VPN doesn't reset them back and of course re-attempting to build will fail. However if I reboot my MacBook, then the keychain is back in a good state again. However as I work remotely I constantly have to flick VPN on and off throughout the day, and having to reboot endlessly is a pain. Is there something I can do to reset the Keychain's certs to a good state without having to reboot? (and without having to delete them all and re-add them all back to the keychain).

I posted this before and thought I had fixed it, but I did not. I have an app which used to work well but now fails to launch the destination Mac (Designed for iPad). It builds fine, but doesn't launch. It does launch as aa Mac Catalyst app and if I modify the bundle id slightly, it launches as a Mac (Designed for iPad) app. I have a very similar, and I mean very similar, project that does not have this problem. I have automatically managing signing checked. would like and appreciate any help you can give me that would help me to solve this problem. I had a feedback on this, but closed it when I thought I had fixed the problem by changing the bundle id, running and then changing the bundle id back. I get the following error information. Could not launch “App Name” Domain: IDELaunchErrorDomain Code: 20 Recovery Suggestion: Runningboard has returned error 5. Please check the system logs for the underlying cause of the error. User Info: { DVTErrorCreationDateKey = "2023-09-27 03:23:51 +0000"; DVTRadarComponentKey = 968756; IDERunOperationFailingWorker = IDELaunchServicesLauncher; } The operation couldn’t be completed. Launch failed. Domain: RBSRequestErrorDomain Code: 5 Failure Reason: Launch failed. Launchd job spawn failed Domain: NSPOSIXErrorDomain Code: 153

As I mentioned elsewhere, I am trying to add a packet filter to our app. I can load load the extension, but I am getting permission denied when I try to save the preferences with it. I am building for release, using a Developer ID Application certificate (macOS, if that wasn't clear). I am starting to worry that I can't do this except on an MDM-managed system.

I had dealt with this in cmake, and then forgotten about it -- now trying my Xcode-only test project, and it won't work, because the profile has -systemextension as a suffix, while the one Xcode generates doesn't. Am I missing something in how to get Xcode to deal with this?

Our provisioning profile expired yesterday. I've created a new distribution profile. And download and installed the certifcate on the MAC I also downloaded and installed the provisioning profile and verified it with: /usr/bin/security cms -D -i <id>.mobileprovision When I run my build script, it fails on this step: Could not find any available provisioning profiles for ..

Hi again still going round in circles here trying to get id certs for ios project. I am working on widows platform and cant get Xcode to download from Apple store.

We are launching a commandline golang binary as daemon. However, SecKeyCreateRandomKey does not return in macos Sonoma. We tried to attach entitlement to the daemon, but it's still not working. The same commandline golang binary works when we launch it as a user process. We would like to get your support to fix this issue.

Dear Sirs, for quite a while I cannot sucessfully invoke "Download Profile ..." anymore inside my XCode macOS project in the Signing section. Nevertheless I can create the profile manually in my developer account and download the provisioning profile to my machine and then invoke "Import Profile ...". That works correct. But also the Identifier is not added anymore automatically to my developer account when I create a new project in XCode. Both things worked correct at the beginning but it could be it got broken after some OS or XCode update. I tried to find logs showing the communication between XCode and my developer account as I think there could be some mismatch somewhere but so far I didn't find anything useful. Although I can do all the things manually it would be nice to have it working again and any hint would be appreciated. Thanks and best regards, Johannes

Hi, I'm looking for a way to allow two TeamID in a PPPC predicate. When an app move from one company to another (different TeamIDs) PPPC configuration profiles need to cover the transition period. However those profiles do not allow duplicated path-based entries. Then the binary /usr/bin/local/sample can have only one PPPC payload for full disk access authorizations. To solve this problem I'd like to use an OR operator in the predicate, such as: identifier Sample and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and (certificate leaf[subject.OU] = TEAMID001 or certificate leaf[subject.OU] = TEAMID002) But I cannot find any documented information about the supported syntax. Does anybody already did this before ?

Hi, After spending two months trying to launch this app I decided to start from scratch, and regenerate everything from code signing requests, certs, apps, appIDs, App Store entries, EVERYTHING, and at the end of all of it, I get exactly the same problem I've had for months: "Invalid Provisioning Profile. The provisioning profile included in the bundle com.chiltonwebb.secretprojectname [com.chiltonwebb.secretprojectname.pkg/Payload/secretprojectname.app] is invalid. [Invalid 'com.apple.application-identifier' entitlement value.] For more information, visit the macOS Developer Portal. (ID: 723cede2-3c9f-4069-b4fa-581ebd3468b9)" I'm tired of guessing. I've tried everything I can find in these forums. What is the official way to diagnose this problem? -Chilton

Hello, I'm working on an app with a local push provider. I already push it on testflight, two weeks ago and before that, and all worked. Since, I updated to Version 15.0.1 (15A507) and download iOS 17. And now I can't upload a build anymore. There is no error on build, I can archive the project, but while I Distribute the app on testflight, it failed. I got this error: I already check my too provisioning profile and the app id (the app one and the localPushProvider one), the two seems to be good. No red cross on Xcode profile analyze for either, with all needing information: This entitlements on each side : <key>com.apple.developer.networking.networkextension</key> <array> <string>app-push-provider</string> </array> I'm running out of clue for fixing this. All of this was working two weeks ago and I don't understand how update my system can interact with upload system ? Any idea what to try to upload my build on TestFlight ? Thank you by advance !

I'm experiencing an issue trying to install the 'mirroringworkoutssample' app from the official Apple documentation on my Apple Watch. When attempting a direct installation from the Apple Watch, I receive an error stating, "Cannot install this app due to an inability to verify its integrity." Has anyone else encountered this problem or can provide any solutions or insights? ** I have a 'Development' type certificate that allows for watchOS(it includes iOS, tvOS ..) development. ** also added WKCompanionAppBundleIdentifier com.example.apple-samplecode.MirroringWorkoutsSample7C76V3X7AB.watchkitapp

Hey guys, I'm trying to build a game using GameMaker Studios for iOS but running into this automatic signing issue - I haven't had this issue on past builds, so it's confusing as to what this is. Any ideas of what I could try to solve this? I've tried many solutions but with my limited knowledge I haven't gotten very far - thank you!

We requested the In-App Provisioning entitlement and received the email from Apple said： “The entitlement for In-App Provisioning has been assigned to your account, and you can now configure this capability for eligible apps. ” Then we enabled the In-App Provisioning capability in the Additional Capabilities tab of App ID Configuration, and according to Apple’s instruction, there should be an entitlements drop-down menu in the provision profile edition page，but we‘ve never seen such menu in our provision profile. So is there any suggestion about this problem？

Hello fellow developers, I hope you're all doing well. I've encountered an issue that I'm hoping someone here might have some insights on. When I try to package my IPA for the production version, I receive a notification that the provisioning profile doesn't match the private key certificate. However, when packaging for the test version, everything works perfectly. I've ensured that I'm using the provisioning profile for the production version and even exported the key for this profile, but they still don't seem to match. Upon further inspection, I noticed that when I applied for the production version of the mobileprovision, the Certificate Name automatically changed to the company name. Has anyone else experienced this issue? If so, how did you resolve it? Any guidance would be greatly appreciated. Thank you in advance for your time and assistance. Best regards

I do NOT have an iPhone or iPad and I need to create a provisioning profile to configure the signing in my Xcode project. I have tried "iOS App Development" profile, but it required adding an iPhone. I have later tried creating an "Developer ID" provisioning profile, which redirects to creating a certificate, choosing "Apple Development" certificate created with an CRS from my Mac. However, this certificate cannot be used to then create the corresponding profile as I was expecting. I trying to create a Provisioning Profile to manually import it into Xcode instead on the automatically managed signing option, since it is not working.

Hi all I have made an application on Windows Adobe Animate /Air ios. when I tried to get a provisioning profile from Adobe, they said I would have to get this from Apple. So I had to join an Apple developers program which I did at a cost of £79 non-refundable. I began to make up my Provisioning profile on apple developers site and at the very end of the process it told me to press a dedicated button on my Apple computer well I don't have an Apple computer that's why I made the application on Windows Adobe Animate with Air ios converter. When I pointed this out to Adobe their reply was to ask Apple if there is a way round this problem. Well I am asking you guys, is there a way round this? Alan