provisioning-profile

问题 Team, We are releasing new update to our project, In the last version we dont have Push Notifications now are implementing all the process. We work for a client where we used to send ipa file with our distribution profile (Push notifications are working for the ipa we are sending). Once we send the working ipa, they will resign the ipa with there Distribution Profiles and Upload to appstore. We have checked all the scenarios like, App Id enabled with Push Notification,SSl generated for

问题 I have used HomeKitCatalog code to communicate with Home app to execute scenes and add accessory. It works as expected in app in foreground. When my app went to background/suspend mode, sending silent notification run scene. But it throws exception " Missing entitlement for API ". Is it related to provisional profile issue? Can anyone help to move forward? 回答1: Developer can't control HomeKit from background https://forums.developer.apple.com/thread/22279 来源： https://stackoverflow.com

问题 I have configured pipeline to build an iOS app that is also an AUv3 plugin, it requires two provisioning profiles but I can't manage the Plist to allow the signature for both. I have installed .p12 and Apple Provisioning Profiles. This is my Xcode task: steps: - task: Xcode@5 displayName: 'Xcode build' inputs: actions: 'build' sdk: iphoneos13.7 xcWorkspacePath: ‘project_name/project.xcworkspace' scheme: 'project_name - All' packageApp: true exportPath: output/ exportOptions: plist

问题 I have configured pipeline to build an iOS app that is also an AUv3 plugin, it requires two provisioning profiles but I can't manage the Plist to allow the signature for both. I have installed .p12 and Apple Provisioning Profiles. This is my Xcode task: steps: - task: Xcode@5 displayName: 'Xcode build' inputs: actions: 'build' sdk: iphoneos13.7 xcWorkspacePath: ‘project_name/project.xcworkspace' scheme: 'project_name - All' packageApp: true exportPath: output/ exportOptions: plist

来源： https://stackoverflow.com/questions/56674618/store-bitrise-provisioning-profiles-in-the-git-repository

来源： https://stackoverflow.com/questions/56674618/store-bitrise-provisioning-profiles-in-the-git-repository

问题 This might have been asked lots of times, but still I couldn't find info on why are they needed. I use DEVELOPER prov profiles to test apps on my device, that makes sense. The Provisioning Portal explains prov profiles like this: A Provisioning Profile is a collection of digital assets that uniquely ties developers and devices to an authorized iOS Development Team and enables a device to be used for testing. By this logic they are only needed for testing, eg not for distribution. Do we need

问题 I currently have problem with my pipeline in Azure Devops. Since March 27th, I got the error: error: Alamofire does not support provisioning profiles. Alamofire does not support provisioning profiles, but provisioning profile prov profile name has been manually specified. Set the provisioning profile value to "Automatic" in the build settings editor. (in target 'Alamofire') I have this error for all my pods. The code: The exact same branch have built correctly the day before. Xcode version: I

问题 After updating to Mavericks and making sure I got the latest updates of Xcode installed as well, Xcode suddenly fails to launch apps on the device. It installs the app on my iPhone but then before running it, throws this error: Process launch failed: Failed to get the task for process 216 This is how the Code Signing settings look like since the update: Also checked Scheme and it runs in Debug configuration. Is this a known issue with Mavericks? How to fix it? 回答1: I got this error when

问题 After updating to Mavericks and making sure I got the latest updates of Xcode installed as well, Xcode suddenly fails to launch apps on the device. It installs the app on my iPhone but then before running it, throws this error: Process launch failed: Failed to get the task for process 216 This is how the Code Signing settings look like since the update: Also checked Scheme and it runs in Debug configuration. Is this a known issue with Mavericks? How to fix it? 回答1: I got this error when