We have a MacOS app that we distribute outside of the App Store. The App has an embedded provisioning profile that is still valid. We would like to add the Associated Domains capability to the app ID. Does that require regenerating a new provisioning profile and embedding it into a new version of App? If we do that, does that mean that the old provisioning profile will become invalid and the old Apps that are still running with it will stop working? Is there a way to make the transition to the new provisioning profile smooth without any downtime?

We have requested an additional capability called "User Assigned Device Name" for my application to Apple and got approved the same on for debug/adhoc/release environments . Since then we are facing issues on code signing. We are always getting the compiler error "* Provisioning profile "xxxxxxxxxxx" doesn't support the User Assigned Device Name capability." on both Debug and Release environment. There is another capability "contacts notes entitlements" that we got approved long back when it was not apart of Apple ID(additional capabilities) rather we got approved as a part of our provisioning profile. Suppose we removed "contacts notes entitlements" from the profile and deleted it from the entitlement folder the project compiled without any error. So we are strongly believes the conflicts on the "contacts notes entitlements" is the root cause. We are about to release the version and which is blocked due to this error. So kindly look in to this issue and do the needful asap. STEPS TO REPRODUCE Added user assigned device name capability from Signing & Capability Tab in project in settings. Added the team, valid provisioning profiles and try to sign in manually. Getting the error “Provisioning profile xxxxxxxxxxxx" doesn't support the User Assigned Device Name capability." Note: Already got approval for the “user assigned device name” . Which is listed under the app id.

我创建了一个developer id instanller 证书，并且安装在自己电脑上，我使用productbuild --component xx.app /Applications --sign "Developer ID Installer: " --product xx.app/Contents/Info.plist ST.pkg签名并生成pkg，使用 spctl -a -v --type install ST.pkg 去验证签名的时候，出现rejected source=Unnotarized Developer ID，我不知道哪里有问题，将pkg安装到其他电脑也会出现pkg无法打开，apple无法检查是否包含恶意软件 提示信息，希望可以得到大家的帮助谢谢，

0 * H ÷   0 1 0 ` H e 0 8 * H ÷   ) % Apple Confidential Profile. Do not distribute. Not to be used or disclosed without permission from Apple. Copyright © 2023, Apple Inc. All rights reserved. PayloadContent PayloadContent DefaultsData SeedGroup PublicBeta DefaultsDomainName .GlobalPreferences DefaultsData SeedProgram PublicSeed DefaultsDomainName com.apple.seeding DefaultsData SBIconVisibility DefaultsDomainName com.apple.appleseed.FeedbackAssistant DefaultsData MobileAssetAssetAudience 48407998-4446-46b0-9f57-f76b935dc223 MobileAssetSUAllowOSVersionChange MobileAssetSUAllowSameVersionFullReplacement MobileAssetServerURL-com.apple.MobileAsset.MobileSoftwareUpdate.UpdateBrain https://mesu.apple.com/assets/iOS17PublicSeed MobileAssetServerURL-com.apple.MobileAsset.SoftwareUpdate https://mesu.apple.com/assets/iOS17PublicSeed MobileAssetServerURL-com.apple.MobileAsset.SoftwareUpdateDocumentation https://mesu.apple.com/assets/iOS17PublicSeed DefaultsDomainName com.apple.MobileAsset PayloadIdentifier com.apple.applebetasoftware PayloadType com.apple.defaults.managed PayloadUUID 617630D8-C055-40A1-A4E8-AC30FD8A5ACE PayloadVersion 1 PayloadDescription Configures your iOS/iPadOS device for use with the Apple Beta Software Program. PayloadDisplayName iOS 17 & iPadOS 17 Beta Software Profile Beta Software Profile PayloadIdentifier com.apple.applebetasoftware PayloadOrganization Apple Inc. PayloadRebootSuggested PayloadType Configuration PayloadUUID 0C90EE68-9104-4D65-80A5-538784AAE2BE PayloadVersion 1 RemovalDate 2025-01-31T00:00:00Z TargetDeviceType 1   s0 0   ¹ûe J i0 H ÷ 0b1 0 U US1 0 U Apple Inc.1&0$ U Apple Certification Authority1 0 U Apple Root CA0 130524174337Z 280524174337Z0 1@0> U 7Apple Application Integration 2 Certification Authority1&0$ U Apple Certification Authority1 0 U Apple Inc.1 0 U US0 "0 H ÷ 0 ¸H¡glV åpÅFô¯…ã½:Þ¡çÙ¨6< b¥|  G³k ¬þØtæ 5°XOtØ£þí-î¤s%YÔ Ü&Ï ' T Ü ±à3 b ȹ¯6 ¤j § mÝÝ -Ì } Ì) £É ª¢ìÙ gi < ¿D($±Ä,5Ö± %ïP§ Û%ÆÃOo[ ¾ñ §Ôl^²9. ©ám ;®9q? ó¹ôW #O ^ ð X¾µÑìײ~Âeâñì<¦ünÛV³î ² KÉ¢ðñ1ö®Þ5là ^Pc ¶ºm\Àã & J Þ ©°Zoû k ìÝß2Þü.B¢ÊxZ× £ ¦0 £0 U ÷¾|! Û= {Ø:2 iß l 0 U ÿ 0 ÿ0 U # 0 +ÐiG v þôk .@¦÷GM ^0. U '0%0# !  http://crl.apple.com/root.crl0 U ÿ 0 * H ÷cd 0 * H ÷ Í ý¤]õñÀ I ݳ3 ­ Ð! ãÙÖÚ¯ " <YBñ- ¶?ÿôôî jxÁ.û;L ®eCËϨ ë=7 E/ J ¨ k â Ûïg¸ ñäØ qwÓó ௤ê( ¤?4ye6 T Aq× !ÜPUEÎ ¼÷ÜUгÊ(Q¬sQ ¬y n  7 a1/¡Ñºëá\7ÀØÑ çà RB¤ ö"| À?Á …ÕÂ'c°bV í%ôÌ ÜT ·yè …8@¹ íMbÔ+ö) ñg¡á r w ö  +Q Sòó óè¿¡ &Ïü 7»@0 S0 ;  À6 k 0 * H ÷ 0 1@0> U 7Apple Application Integration 2 Certification Authority1&0$ U Apple Certification Authority1 0 U Apple Inc.1 0 U US0 201214200231Z 231214200231Z0s1.0, U %AppleCare Profile Signing Certificate1 0 U Configuration Profiles1 0 U Apple Inc.1 0 U US0 "0 * H ÷ 0 Ú ûñ E0H( ì ¶A¤[ûB JVßúLWæýøÖf ö×ïÃWWÀ[kh ³oíR téAj ³ » Q¬w é ÷;$Þ #Àå °»¤ýg Bªb}ÏñAó,³! ÄûÑhsÏû ê ÒdËt©P +ñ üûSï fÄ eï2ÝV^"þïÑ8 {H ôF ¯ÉU w. ×N_ Ü H $&uwY``éL5 õ îÚzø OÝ ¿Ó r¡ëD;HÒ y åÈH'>øÊ ØòÖQnÜ ° +ùl· TÚ ç2 S¥ÿQ ¾*i'¥\ ?W°ßº"zoS5Sû¢ÔÑ"XÜ/ £ Ï0 Ë0 U ÿ 00 U # 0 ÷¾|! Û= {Ø:2 iß l 0@ + 40200 + 0 $http://ocsp.apple.com/ocsp04-aaica020 U 0 0 þ H ÷cd 0 ð0( + http://www.apple.com/appleca0 à + 0 ¶ ³Reliance on this certificate by any party assumes acceptance of the then applicable standard terms and conditions of use, certificate policy and certification practice statements.0 U % ÿ 0 H ÷cd 0 U 9S öÇGÔÆ?£l% ê$% º·0 U ÿ 0 * H ÷ Sß3çhÂ- 3=%à¬q dÙ ER ÷ ßù¾) ?nC ØÎò, ]¶OLE. |g#æ Qg% Ǽ ªë K · Êç S¥Oï p4 Ú¾ ²Õ ë( ÷¸Ìæs¾ ¦æ@ Äç0AFï t,Th ÏEi § |ààÞ Ú:K q÷Ûø·É õ y¬[$GÉ ø ­¤HÞÖ Ü w +÷p ¥A¥ ]z ] ï òé/ ûö tîPøSo¿­Ä|à IlÓV¾é * ä<ÈçÌÈ ïø¯f°3 Æ5 s¸ x¦cPb b ÉU ´V×&ñ¦ èv¹ |:¯"Ð hŲ1 =0 9 9S öÇGÔÆ?£l% ê$% º·0 H e 0 * H ÷ ûÄÄD úªÀg ¸« y6íÛÜ*ú ºÝ¤¢ ~/vÝæBx ąæ,þPß ò Âï…j¦·tu¾ðì×v 5ã¸pñ ìçó%¡Òª ±Q| ½ jÆË ü fK0 $ö4 }| `óq( ÈÄ· ®jÈÑ §?)ÍTÀ a ìø&¸7¡ï#¼£> Îer ¤ÑÍ ¨ \zHkN© <5 ýò¼F4ó »¨"\ Á Ô dêGivo&D օY\¸ì äAÏáî lã!1À ±_4ñ g4t Cá ² !~)Hî Æ$ ã¦Úø)>e ,èòSûtÖ·ú$,y

I'm trying to install from Xcode (15.4) to my physical device (iPhone SE 3rd gen, iOS 17.5.1) but I get the following error. My provisioning profile is from a 3rd party organization, but I have confirmed my device UUID is added to their account and that the profile does contain the beta-reports-active flag. I have also checked that this is added to the entitlements file. It works fine it I deploy and install via TestFlight, but for obvious reasons I would prefer not to have to do that for each and every build. Can anyone suggest how to resolve this, either with local config or by asking the account admin to modify the provisioning profiles? Unable to Install “[redacted]” Domain: IXUserPresentableErrorDomain Code: 14 Recovery Suggestion: Failed to install embedded profile for [redacted] : 0xe800801f (Attempted to install a Beta profile without the proper entitlement.) User Info: { DVTErrorCreationDateKey = "2024-07-03 12:47:34 +0000"; IDERunOperationFailingWorker = IDEInstallCoreDeviceWorker; } -- Unable to Install “[redacted]” Domain: IXUserPresentableErrorDomain Code: 14 Recovery Suggestion: Failed to install embedded profile for [redacted] : 0xe800801f (Attempted to install a Beta profile without the proper entitlement.) User Info: { IDERunOperationFailingWorker = IDEInstallCoreDeviceWorker; } -- Failed to install the app on the device. Domain: com.apple.dt.CoreDeviceError Code: 3002 User Info: { NSURL = "file:///Users/dan/Library/Developer/Xcode/DerivedData/iosApp-gxsprezneuyftnhbmfyfssbeojgd/Build/Products/Debug%20development-iphoneos/[redacted].app/"; } -- Unable to Install “[redacted]” Domain: IXUserPresentableErrorDomain Code: 14 Failure Reason: This app cannot be installed because its integrity could not be verified. Recovery Suggestion: Failed to install embedded profile for [redacted] : 0xe800801f (Attempted to install a Beta profile without the proper entitlement.) -- Failed to install embedded profile for [redacted] : 0xe800801f (Attempted to install a Beta profile without the proper entitlement.) Domain: MIInstallerErrorDomain Code: 13 User Info: { FunctionName = "-[MIInstallableBundle _installEmbeddedProfilesWithError:]"; LegacyErrorString = ApplicationVerificationFailed; LibMISErrorNumber = "-402620385"; SourceFileLine = 308; } -- Event Metadata: com.apple.dt.IDERunOperationWorkerFinished : { "device_isCoreDevice" = 1; "device_model" = "iPhone14,6"; "device_osBuild" = "17.5.1 (21F90)"; "device_platform" = "com.apple.platform.iphoneos"; "dvt_coredevice_version" = "355.28"; "dvt_mobiledevice_version" = "1643.100.60"; "launchSession_schemeCommand" = Run; "launchSession_state" = 1; "launchSession_targetArch" = arm64; "operation_duration_ms" = 3497; "operation_errorCode" = 14; "operation_errorDomain" = IXUserPresentableErrorDomain; "operation_errorWorker" = IDEInstallCoreDeviceWorker; "operation_name" = IDERunOperationWorkerGroup; "param_debugger_attachToExtensions" = 0; "param_debugger_attachToXPC" = 1; "param_debugger_type" = 3; "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_checker_tpc_enable" = 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" = 99; "param_launcher_substyle" = 8192; "param_runnable_appExtensionHostRunMode" = 0; "param_runnable_productType" = "com.apple.product-type.application"; "param_structuredConsoleMode" = 1; "param_testing_launchedForTesting" = 0; "param_testing_suppressSimulatorApp" = 0; "param_testing_usingCLI" = 0; "sdk_canonicalName" = "iphoneos17.5"; "sdk_osVersion" = "17.5"; "sdk_variant" = iphoneos; } -- System Information macOS Version 14.3 (Build 23D56) Xcode 15.4 (22622) (Build 15F31d) Timestamp: 2024-07-03T13:47:34+01:00

Hello, after migrating one of our apps, APP, from the one developer account to another, we are experiencing an issue with provisioning profiles. In the provisioning profile of APP (com.SOME.APP), we have a wrong value for the com.apple.developer.ubiquity-kvstore-identifier key used for iCloud KVS. The value is OLDTEAMID.com.SOME.APP.EXTENSION while it should be just OLDTEAMID.com.SOME.APP. The previous value must be instead present in the provisioning profiles for the EXTENSION (OLDTEAMID.com.SOME.APP.EXTENSION) for the com.apple.developer.ubiquity-kvstore-identifier key. Please let me know if you know something about this issue. This is blocking us from releasing the application. Thank you!