Currently, the id of my actual visionpro device is different from the xcode that works on my macmini. I added a visionpro id to xcode, but I can't build it with my visionpro. Can I log out of the existing login to xcode and log in with the same ID as visionpro? However, the appleID created for visionpro does not have an Apple Developer membership, so there is no certificate that makes it run on the actual device. How can I add my visionpro ID from the ID with my apple developer membership to run the xcode project app on visionpro? This is the first time this is the first time.

According to the WWDC202310224 "Simplify distribution in Xcode and Xcode Cloud" video, there are two questions about my development process. First, the developer must use "Development Profile" to config Signing & Capability instead of "Developer ID Application profile" for building Applications? shown as the pictures below Second, after build application successfully with "Development Profile", process Product -> archive will fail with "Command SetOwnerAndGroup failed with a nonzero exit code" error message, I have no idea how to solve this problem. Cloud you please tell me how to successfully archive the DriverKit application step by step and further directly distribute Application ? Thanks for your helpful support.

I'm experiencing an issue while attempting to create a provisioning profile for push notifications. But I can clearly see that the push notification service is enabled for the new provisioning profile. However it still shows error.

I want to update the provisioning profile from the developer account. There were errors in the data supplied. Please correct and re-submit. No value was provided for the parameter 'appIdId'. No value was provided for the parameter 'provisioningProfileName'. Does anyone know how to fix this error?

Hello all professions, I'm now facing an problem with distribution certification expiration for the enterprise account. We're using enterprise account for publishing some internal apps for our organization without uploading to AppStore but by other platforms, but both cert and profile have 1 year expiration and now it's about to expire. So we're going to extend the app expiration date now. Read some articles that the best practice is renewing cert before it expired, for some reasons that we CANNOT add new certifications if we're not revoking any of existing certs, so what we are going to do is: We will revoke the cert first let's say certA, and then create a new cert with all configurations as same as certA let's say certB and then distribute new app version by certB. If we're going to do so, then the question comes: Will the existing installed apps distributed by certA still available? (if it has couple months to be expired for certA) Continue with question1, if no, all existing apps will not be available anymore, then what's the best practice for us to manage certs and app for the users without cert renewing downtime? Will there be any issue if we user another cert let's say certC just create now to distribute new app version without revoking current certA? such as it will be recognized a brand new app, etc thanks all

After updating the os to iOS17 beta, not able to install the enterprise app through ipa, it throws error Error installing '//Downloads/-Internal-Appstore-23.6.5-1.ipa', ERROR: Error Domain=com.apple.dt.CoreDeviceError Code=3002 "Failed to install the app on the device." UserInfo={NSUnderlyingError=0x600019bcc750 {Error Domain=com.apple.dt.CoreDeviceError Code=3000 "The item at -Internal-Appstore-23.6.5-1.ipa is not a valid bundle." UserInfo={NSURL=file:////Downloads/-Internal-Appstore-23.6.5-1.ipa, NSLocalizedDescription=The item at -Internal-Appstore-23.6.5-1.ipa is not a valid bundle., NSLocalizedFailureReason=Failed to read the bundle.}}, NSLocalizedDescription=Failed to install the app on the device., NSURL=file:///Downloads/-Internal-Appstore-23.6.5-1.ipa} Kindly update on this. Do any code side changes have to be done for this to fix these issue?

I am trying to register my iPad as a device on the developer portal but it keeps declaring it as an iMac. Do you know if this is a typical problem?

Hello, I have an iOS mobile application. I want to wrap this application using an app wrapping tool and distribute it in Microsoft Intune MDM. (I want to perform the process in the link below.) https://learn.microsoft.com/en-us/mem/intune/developer/app-wrapper-prepare-ios#steps-to-create-an-apple-signing-certificate In the "Steps to create an Apple signing certificate" section of this link, the application is signed as In-House. However, I cannot see the In-House option in my Apple Developer account. I only see the options in the image below. My developer account type is "organization." Why can't I see the In-House option in Distribution? What should I do for this?

I am stuck. I have an iPadOS app that installs and calls a DEXT. I have a provisioning file for the DEXT and another for the app. Xcode shows me that the respective provisioning files match the bundle ids and that the entitlements and provisions match up. I have a developer certificate (two, actually) on the iPad. Xcode shows me, via "Devices" that the provisioning files are installed. When I try to run the app, I get: 0x16d3db000 +[MICodeSigningVerifier _validateSignatureAndCopyInfoForURL:withOptions:error:]: 78: Failed to verify code signature of /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.vyncZ7/extracted/USBApp.app/SystemExtensions/w1ebr.MUUI.ipadOS.driver.dext : 0xe8008015 (A valid provisioning profile for this executable was not found.) I don't know what to check next.

We have one enterprise app and for which Provisioning profile got expired and all our user's app stop working. We haven't received any reminder mail from Apple to update the Provisioning profile. We used to get the reminder mail before expiry of any Apple certificate. What is the solution for this? Do we need to manually keep track for Provisioning profile expiry?

I have been an inactive app developer for years, and also have a new MacBook in which I restored from my Apple Time Machine where my source code was stored. I have renewed my apple developer membership. When I tried to build my app, I received the following error:Unable to login with account "sampleaccount" sign in and try again. I cannot reset that password, because that email address does not exist anymore. How can I change this account to my current email address? If I cannot change it then what are my options? I would like to use the email address that I use to log into developer.apple.com with.

I send a macOS app build to appStoreConnect. The app is displayed inside TestFlight but when I click on it to open it, two modal appear. The first one: the application "AppName" can't be opened. -10673 The second one: "AppName" No longer Available. The beta app, AppName, is no longer available. The provisioning profile is invalid. I followed the following step before uploading the app archive: I made sure to purge my Mac from all the old provisioning profile having all my provisioning profile from my apple developer account valid retrieve provisioning profile Xcode settings > Accounts to export an archive. I choose TestFlight & App Store to send the Archive. I am still no understanding which part of my provisioning profiles are not valid, I would love to have insight about it or a way to fix the issue.

We asked for and received confirmation that we have received the Critical alert entitlement. I have also tested it in development build with a development profile and it worked. However when we try to send an update to test flight to test in release mode on our device, we get the following error: The bundle contains a key that is not included in the provisioning profile: 'com.apple.developer.usernotifications.critical-alerts' NSLocalizedFailureReason = "Invalid Code Signing Entitlements. The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. The bundle contains a key that is not included in the provisioning profile: 'com.apple.developer.usernotifications.critical-alerts' in our app. SUnderlyingError = "Error Domain=IrisAPI Code=-19241 "Asset validation failed" UserInfo={status=409, detail=Invalid Code Signing Entitlements. The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. The bundle contains a key that is not included in the provisioning profile: 'com.apple.developer.usernotifications.critical-alerts in our app code=STATE_ERROR.VALIDATION_ERROR.90163, title=Asset validation failed we added the following entitlement to the entitlements.plist file: com.apple.developer.usernotifications.critical-alerts

I registered a Mac as a device in apple-developer using a third-party UID for collaboration, but the Mac cannot be selected when creating a provisioning profile. And they say udid and uuid are the same. Why is that? The third party's Mac has been updated to Ventura OS using Open Core patcher.

We've got 3 MacOS apps on TestFlight that all suddenly became unusable to our testers who upgraded the OS to 14.2. The error message says: "The application can't be opened. -10673" But also there was another window that opened up stating "The beta app, , is no longer available. The provisioning profile is invalid" The provisioning profile doesn't specify OS versions - it's signed with distribution and installation certificates for AppStore. These apps have been used that's been successfully provisioned, uploaded, downloaded and tested by various testers prior to now. Each app has an explicit Apple ID and provisioning profile - all still valid. What would cause this? How can I fix this?

Hi all, I'm attempting to test integration of the Sensitive Content Analysis (SCA) framework in my iOS application. To do so, my understanding is that I need to install the SCA debugging profile in order to generate false-positives. However, when I attempt to download and install the profile on my iOS device, I receive this error message: The error message indicates that the "Profile 'SensitiveContentAnalysis Debug Profile' has an invalid signature." Is there something on my device that's improperly configured and preventing its installation, or does the linked debug profile from Apple really, truly contain an invalid signature?

To be able to paire a matter device on ios I need to installed on my iPhone the matter client developper profile as indicate on the apple documentation Adding Matter support to your ecosystem | Apple Developer Documentation (To test your app on the iOS or macOS device that initiates the pairing, download the developer profile now, then install it.) When I do that it works perfectly. Otherwise the documentation says that the profile is only needed for development but when I want to use my app from the apple store (validate by Apple) and when I remove the profile it doesn't work anymore. What do I have to do to paire Matter device on iphone without the Matter client developer profile.