I create two Extensions in my continer app. Do I need create diffierent provisoning profiles for these Extensions ?

Hello. I have a problem while im trying to archive my application throw the xcode. I follow instructions about certificates, profiles etc. (i create distributions because i don't have an iphone and while i create the distribution i don't have an option to select a devices) i'm working throw my macBook. After installing certificates and setting up my xcode, i build the app and the trying to archive but i get the following error: Communication with Apple failed Your team has no devices from which to generate a provisioning profile. Connect a device to use or manually add device IDs in Certificates, Identifiers & Profiles. https://developer.apple.com/account/ (i tried manually and automatic throw xcode) (i already added my mac device to devices the developer account.) What the problem is?

I've added my iPhone's correct UDID in the "Devices" section in Apple Developer account, and I created a Development Profile. I then downloaded it (as a .mobileprovision file) and am trying to add it to my connected iPhone via XCode. I'm getting this error message: Failed to install one or more provisioning profiles on the device. Please ensure the provisioning profile is configured to this device. If not, please try to regenerate a new profile. I have ensured the provisioning profile is configured to this device and have tried regenerating it. Same result. My iPhone has "Developer Mode" turned on. How do I troubleshoot this further?

Hello, Can anybody help me with some info about the following situation? We have an app that is published in the store and it is used by the users. We want implement in the app the In App Provisioning flow and we are analyzing all the steps the we need to check. One of the steps is the request for a special entitlement from apple. Let's say that we've checked the following: Request In App Provisioning entitlement Receive the entitlement Create a new provisioning profile with the received entitlement Start the development of In App Provisioning flow in the app At some point a bug is identified in production and we need the develop a hotfix that needs to be published before finishing the In App Provisioning feature. Wil it be possible to publish a new version of the app that doesn't contain the In App Provisioning functionality even though we have received the entitlement from apple? Should we create a new provisioning profile without the entitlement for this new release? Please let me know if you need more info.

I have an app already uploaded to app store and its bundle id is service id not app id and i have an update with this app and when i tried to upload a new versions i found errors with bundle id registration and that is no Provisioning Profiles found for this bundle id so i tried to create new Provisioning Profiles with the service id that already connected with my app on app store connect and no luck to create Provisioning Profiles for service id and i cannot now upload a new updates

In 2016 we have to paid 99$ to test on a device. in 2017 we don't need to paid this taxe,if we test with a single device. Now is it possible, I don't see it ? if no since ? Thanks

Everything is ok util upgrade to xcode15.3 and macos14.0. When I usexcodebuild to build my app, some error occured: error: "ShopAssistant" requires a provisioning profile with the Associated Domains, Push Notifications, and Sign in with Apple features. Select a provisioning profile in the Signing & Capabilities editor. (in target 'ShopAssistant' from project 'ShopAssistant') But, just use Xcode menu Product/Archive is ok. I need to use command line in our CI/CD system. Hope somebody can help me. Terminal Log Details: xcodebuild -project ShopAssistant.xcodeproj -scheme ShopAssistant -sdk iphoneos -configuration Release archive Command line invocation: /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -project ShopAssistant.xcodeproj -scheme ShopAssistant -sdk iphoneos -configuration Release archive User defaults from command line: IDEPackageSupportUseBuiltinSCM = YES Build settings from command line: SDKROOT = iphoneos17.4 --- xcodebuild: WARNING: Using the first of multiple matching destinations: { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device } { platform:macOS, arch:arm64, variant:Designed for [iPad,iPhone], id:00008103-0009489814FB001E, name:My Mac } { platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device } { platform:iOS Simulator, id:E06C0B90-67C7-449D-981E-0BFEEDF77160, OS:17.4, name:iPad (10th generation) } { platform:iOS Simulator, id:E06C0B90-67C7-449D-981E-0BFEEDF77160, OS:17.4, name:iPad (10th generation) } { platform:iOS Simulator, id:35BC8560-1097-4751-A0F5-F6DC0B4C84DE, OS:17.4, name:iPad Air (5th generation) } { platform:iOS Simulator, id:35BC8560-1097-4751-A0F5-F6DC0B4C84DE, OS:17.4, name:iPad Air (5th generation) } { platform:iOS Simulator, id:1150700F-45CA-42E4-8D8B-8E70C849886E, OS:17.4, name:iPad Pro (11-inch) (4th generation) } { platform:iOS Simulator, id:1150700F-45CA-42E4-8D8B-8E70C849886E, OS:17.4, name:iPad Pro (11-inch) (4th generation) } { platform:iOS Simulator, id:5BA4C379-2462-449F-9D93-5D64DED7422E, OS:17.4, name:iPad Pro (12.9-inch) (6th generation) } { platform:iOS Simulator, id:5BA4C379-2462-449F-9D93-5D64DED7422E, OS:17.4, name:iPad Pro (12.9-inch) (6th generation) } { platform:iOS Simulator, id:F2F80E23-7C33-4965-806D-EC56962ECE54, OS:17.4, name:iPad mini (6th generation) } { platform:iOS Simulator, id:F2F80E23-7C33-4965-806D-EC56962ECE54, OS:17.4, name:iPad mini (6th generation) } { platform:iOS Simulator, id:C5A161D8-1D8B-499A-BB27-3B630002CE25, OS:17.4, name:iPhone 15 } { platform:iOS Simulator, id:C5A161D8-1D8B-499A-BB27-3B630002CE25, OS:17.4, name:iPhone 15 } { platform:iOS Simulator, id:995C11EA-5ACF-4A1A-9FFC-DF0A0AEE63F2, OS:17.4, name:iPhone 15 Plus } { platform:iOS Simulator, id:995C11EA-5ACF-4A1A-9FFC-DF0A0AEE63F2, OS:17.4, name:iPhone 15 Plus } { platform:iOS Simulator, id:3A444CC6-16B1-4F79-8144-7A5BB23FD1BA, OS:17.4, name:iPhone 15 Pro } { platform:iOS Simulator, id:3A444CC6-16B1-4F79-8144-7A5BB23FD1BA, OS:17.4, name:iPhone 15 Pro } { platform:iOS Simulator, id:D30229CD-1D9E-4206-980E-70A5208E5193, OS:17.4, name:iPhone 15 Pro Max } { platform:iOS Simulator, id:D30229CD-1D9E-4206-980E-70A5208E5193, OS:17.4, name:iPhone 15 Pro Max } { platform:iOS Simulator, id:3C53C988-D93B-4E38-AC9F-BE8B8F111280, OS:17.4, name:iPhone SE (3rd generation) } { platform:iOS Simulator, id:3C53C988-D93B-4E38-AC9F-BE8B8F111280, OS:17.4, name:iPhone SE (3rd generation) } Prepare packages ComputeTargetDependencyGraph note: Building targets in dependency order note: Target dependency graph (1 target) Target 'ShopAssistant' in project 'ShopAssistant' (no dependencies) GatherProvisioningInputs CreateBuildDescription ExecuteExternalTool /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -v -E -dM -arch arm64 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS17.4.sdk -x objective-c -c /dev/null ExecuteExternalTool /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -v -E -dM -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS17.4.sdk -x c -c /dev/null ExecuteExternalTool /Applications/Xcode.app/Contents/Developer/usr/bin/ibtool --version --output-format xml1 ExecuteExternalTool /Applications/Xcode.app/Contents/Developer/usr/bin/actool --print-asset-tag-combinations --output-format xml1 /Users/es/ShopAssistant_3.7.9/shopassistant_native_ios_pure/930714_0_4.9.3/Assistant/Images.xcassets ExecuteExternalTool /Applications/Xcode.app/Contents/Developer/usr/bin/actool --version --output-format xml1 ExecuteExternalTool /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc -v ExecuteExternalTool /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -v -E -dM -arch arm64 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS17.4.sdk -x c -c /dev/null ExecuteExternalTool /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld -version_details Build description signature: xxxxxxx Build description path: /Users/es/Library/Developer/Xcode/DerivedData/ShopAssistant-cmrxpudshqxyfcgqsharjobmjuxt/Build/Intermediates.noindex/ArchiveIntermediates/ShopAssistant/IntermediateBuildFilesPath/XCBuildData/xxxxxx.xcbuilddata /Users/ShopAssistant.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 12.0 to 17.4.99. (in target 'ShopAssistant' from project 'ShopAssistant') /Users/ShopAssistant.xcodeproj: error: "ShopAssistant" requires a provisioning profile with the Associated Domains, Push Notifications, and Sign in with Apple features. Select a provisioning profile in the Signing & Capabilities editor. (in target 'ShopAssistant' from project 'ShopAssistant') ** ARCHIVE FAILED **

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!

Hello, We currently have an IOS Mobile app using the ad-hoc provisioning profile with a distribution certificate. We are wanting to renew the ad-hoc provisioning profile BEFORE it expires. How do i do this without causing the application to break AND prevent the user from having to re-trust the. Can i simply create a new ad-hoc provisioning profile associated with the old certificate, rebuild the app, and send the link to the user?

Hello . Currently, only the ios version is on sale on the App Store. The application is offering an icloud-linked, auto-renewable subscription. I want to sell to the app store connect with the same identifier, AppID at the same time. I simply added visionos to the existing app project to provide the visionos version early, but the existing UI-related code and the location-related code are not compatible. We used the same identifier with the same name, duplicated and optimized only what could be implemented, and created it without any problems on the actual device. However, when I added the visionos platform to the App Store cennect and tried to upload it through the archive in the app for visionos that I created as an addition, there was an error in the identifier and provisioning, so the upload was blocked. The result of looking up to solve the problem App Group -I found out about the function, but it was judged that a separate app was for an integrated service, so it was not suitable for me. Add an APP to an existing app project via target and manually adjust the platform in Xcode -> Build Phases -> Compile Soures -> Archive upload success?( I haven't been able to implement this stage of information yet.) I explained the current situation. Please give me some advice on how to implement it.visionos has a lot of constraints, so you need to take a lot of features off.

Currently, I'm reducing the ios version being sold on the App Store with the same app id and identifier to visionos, and I'm trying to upload it using the same identifier, developer id, and icloud, but I can't upload it because of an error. I didn't know what the problem was, so I updated the update of the ios version early, but I uploaded the review without any problems. Uploading the visionos single version has a profile problem, so I would appreciate it if you could tell me the solution. In addition, a lot of the code used in the ios version is not compatible with visionos, so we have created a new project for visionos.

When I try to copy existing provision profile from our onprem mac mini to aws mac mini it is disappeared from the folder . /Users/ec2-user/MobileDevice/Provisioning Profiles/ Not sure whats going here .

The documentation for CarPlay (https://developer.apple.com/documentation/carplay/requesting_carplay_entitlements) tells you to disable automatic signing in the section titled "Import the CarPlay Provisioning Profile": Click All in the scope bar, and then deselect “Automatically manage signing”. There have also been other posts in the past about the inability to use automatic signing with CarPlay: https://developer.apple.com/forums/thread/63468 However in a recent post of mine (https://developer.apple.com/forums/thread/717429?login=true&page=1#732392022) I was instructed how to set it up so that I could use automatic signing for the new user-assigned-device-name entitlement and it worked so I thought "Can I do the same thing for CarPlay?" and it seems to be working so far. Is automatic signing with CarPlay now possible? We have been able to use automatic signing to archive successfully and run to real devices and verify that CarPlay is working. I'm crossing my fingers that we'll be able to submit and get the build approved and never have to touch manual signing again. Hopefully it works and the documentation is just out of date.

Electron-Builder Version: 24.12.0 Electron-Builder-notarize Version: 1.5.1 Node Version: v15.14.0 Electron Version: 11.3.0 Electron-updater version: ^4.3.5 Target: Mac Apple Store (mas) Hello, I am trying to build and sign a new version of my electron app for the mac apple store (mas), but when I get to the final step of uploading the RenderTune.pkg file to the mac transporter app, I get a failed status with 22 errors all the same formatting like so: Asset validation failed (90284) Invalid Code Signing. The executable 'com.martinbarker.digifyunique.pkg/Payload/RenderTune.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/etc....dylib' must be signed with the certificate that is contained in the provisioning profile. (ID: abc-abc-abc-abc-abc) In order to build and sign this RenderTune.pkg file, first I run the command npm run build-mas locally while on branch v1.1.5 ( code here ) Which runs the following command: "build-mas": "electron-builder build --mac && sh signmasscript.sh", So first it runs electron-builder build --mac and gives this output: Martins-MacBook-Air:rendertune-v1.1.5-feb-24 martinbarker$ npm run build-mas > rendertune@1.1.5 build-mas > electron-builder build --mac && sh signmasscript.sh • electron-builder version=24.12.0 os=20.6.0 • loaded configuration file=package.json ("build" field) • writing effective config file=dist/builder-effective-config.yaml • packaging platform=darwin arch=x64 electron=11.3.0 appOutDir=dist/mac • signing file=dist/mac/RenderTune.app platform=darwin type=distribution identity=ACBACBACBACBACBACBACBACBACB provisioningProfile=none • skipped macOS notarization reason=`notarize` options were not provided • building target=DMG arch=x64 file=dist/RenderTune-mac.dmg • building target=macOS zip arch=x64 file=dist/RenderTune-mac.zip • building block map blockMapFile=dist/RenderTune-mac.dmg.blockmap • building block map blockMapFile=dist/RenderTune-mac.zip.blockmap Completes without issue. The next part is running the signmasscript.sh file, which does complete but gives these errors: Failed to parse entitlements: AMFIUnserializeXML: syntax error near line 1 Failed to parse entitlements: AMFIUnserializeXML: syntax error near line 1 Failed to parse entitlements: AMFIUnserializeXML: syntax error near line 1 Failed to parse entitlements: AMFIUnserializeXML: syntax error near line 1 Failed to parse entitlements: AMFIUnserializeXML: syntax error near line 1 Failed to parse entitlements: AMFIUnserializeXML: syntax error near line 1 Failed to parse entitlements: AMFIUnserializeXML: syntax error near line 1 Failed to parse entitlements: AMFIUnserializeXML: syntax error near line 1 Failed to parse entitlements: AMFIUnserializeXML: syntax error near line 1 Failed to parse entitlements: AMFIUnserializeXML: syntax error near line 1 productbuild: Adding component at /Users/martinbarker/Documents/projects/rendertune-v1.1.5-feb-24/dist/mas/RenderTune.app productbuild: Signing product with identity "3rd Party Mac Developer Installer: Martin Barker (LV6WXG529F)" from keychain /Users/martinbarker/Library/Keychains/login.keychain-db productbuild: Adding certificate "Apple Worldwide Developer Relations Certification Authority" productbuild: Adding certificate "Apple Root CA" productbuild: Wrote product to /Users/martinbarker/Documents/projects/rendertune-v1.1.5-feb-24/RenderTune.pkg productbuild: Supported OS versions: [10.10.0, ) The final output RenderTune.pkg file gives 22 error messages saying `` when I try to deliver it via the mac os transport app. Asset validation failed (90284) Invalid Code Signing. The executable must be signed with the certificate that is contained in the provisioning profile Is my app even being signed correctly? Or is there just one file that I need to fix? Please help me out !

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. Developer > Support > Certificates covers some important policy issues Entitlements documentation TN3125 Inside Code Signing: Provisioning Profiles — This includes links to other technotes in the Inside Code Signing series. WWDC 2021 Session 10204 Distribute apps in Xcode with cloud signing Certificate Signing Requests Explained DevForums post --deep Considered Harmful DevForums post Don’t Run App Store Distribution-Signed Code DevForums post Resolving errSecInternalComponent errors during code signing DevForums post Finding a Capability’s Distribution Restrictions DevForums post Signing code with a hardware-based code-signing identity DevForums post Mac code signing: DevForums tag: Developer ID Creating distribution-signed code for macOS documentation Packaging Mac software for distribution documentation 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 Defining launch environment and library constraints documentation WWDC 2023 Session 10266 Protect your Mac app with environment constraints TN2206 macOS Code Signing In Depth archived technote — This doc has mostly been replaced by the other resources linked to here but it still contains a few unique tidbits and it’s a great historical reference. Manual Code Signing Example DevForums post The Care and Feeding of Developer ID DevForums post TestFlight, Provisioning Profiles, and the Mac App Store DevForums post 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"

Hello everyone! I've tried to deliver new build of my app and i got this error: Asset validation failed (90161) Invalid Provisioning Profile. The provisioning profile included in the com.***.app bundle [Payload/app.app] is invalid. [Missing code-signing certificate]. A distribution provisioning profile should be used when uploading apps to App Store Connect. (ID: 5b0ca8f4-werwer-45df-8cc8-3b58fdcce870) I've read and applied a lot of ways to fix that, but unsuccessfully. The app version 1.0.28 is in "Add for Review" and in the TestFlight is 1.0.28 Build 1. I'm trying to deliver version 1.0.28 Build 2 and got this error thousand times. Can you guys help me please?

So here is the thing. I'm trying to upload an app to the app store but I'm facing an irritating challenge. A very frustrating one. No profiles for 'com.company.***' were found Xcode couldn't find any iOS App Development provisioning profiles matching 'com.egonai.iosaiapp'. What is annoying is that I firstly created the bundle identifier myself on my developer account and it did not work. I then even removed the bundle id and let xcode create one automatically but it still doesn't work. The bundle id on both occasion seems to appear on my apple developer account but in xcode it gives me this error. I have nothing to solve this problem. I'm not sure as to how or why is this happening. I would really appreciate it if someone could help fix this problem.

I'm not able to run my app on my device as Xcode is unable to create a provisioning profile for my app without the paid developer membership. I followed the troubleshooting steps on stack overflow here but to no avail. Any help?

Hi , In one of our application we are having issues of bundle Id mismatch in the distribution profile. Say there are two applications X and Y. Issue Description : On the developer portal inside the distribution profile the App Id shown is correct I.e of X but when we download the distribution profile and open it in the textedit we can see that the bundle id is of another application i.e of Y . Due to which are are unable to submit or upload the application. 
 Note: Both of them have contact notes as additional permission.