provisioning-profile

Debug rows missing from Code Signing and Provisioning Profile sections

≡放荡痞女 提交于 2020-01-25 20:26:08
问题 The problem: With All/Combined selected from the top menu within either the Project or the Target, this is what I see. Debug used to be listed within the Provisioning Profile and Code Signing Identity sections, but it is now missing. I can build a run on the simulator like this but when trying to deploy to a tethered testing device I get errors about provisioning profile and code signing being required. This is not a duplicate of 'Provisioning profile' options missing from 'Code signing'

CoreTelephony eSIM functions not working on device

匆匆过客 提交于 2020-01-22 02:32:11
问题 I've been having some trouble implementing eSIM into an existing iOS carrier-application. The setup The app has received the public-cellular-plan entitlement which I understand is the entitlement giving me access to the eSIM functions of CoreTelephony. I've imported the CoreTelephony framework in the app's target: General > Frameworks, Libraries, and Embedded Content which is marked as Do not Embed , same as other frameworks like CoreData and such. I've imported the library in the class

How come I can install an app store distribution build directly on my device?

与世无争的帅哥 提交于 2020-01-19 23:15:11
问题 I was under the impression that it was impossible to install an app store distribution build directly on a test device (without going through the actual App Store). I found multiple references to the following note by Apple (though I could not find the note itself in the current version of the iOS App Distribution Guide): "App Store provisioning profiles do not allow for a distribution built application to be installed on an Apple device. To install your distribution ready application on a

How come I can install an app store distribution build directly on my device?

最后都变了- 提交于 2020-01-19 23:14:29
问题 I was under the impression that it was impossible to install an app store distribution build directly on a test device (without going through the actual App Store). I found multiple references to the following note by Apple (though I could not find the note itself in the current version of the iOS App Distribution Guide): "App Store provisioning profiles do not allow for a distribution built application to be installed on an Apple device. To install your distribution ready application on a

Get the name of provisioning profile in xcode

拈花ヽ惹草 提交于 2020-01-13 19:29:09
问题 I have some expired(unused) provisioning profile in my xcode. I want to delete them but the problem is in my ~/Library/MobileDevice/Provisioning\ Profiles/ folder the provisioning profiles are not saved with the name but a hexadecimal string like 03264601-561e-4185-b6b9-968b168d57a1.mobileprovision 31266708-96d8-4496-88ce-8c2a1681d5c6.mobileprovision 3d26aa08-16ef-4023-a563-ec77168a6043.mobileprovision 4926b573-36f4-4235-9519-5534168b3f9c.mobileprovision 4926eb37-a630-4ca4-989c-0e66168c3795

itunes connect - beta entitlement missing error

好久不见. 提交于 2020-01-13 05:54:09
问题 I create a new App Store Distribution profile containing the beta entitlement to distribute builds via TestFlight, I create my application based on new profile that was contain beta entitlement, when I submit my application I got this error: Generate a new App Store Distribution profile containing the beta entitlement to distribute builds via TestFlight Here is my provision profile: <key>Entitlements</key> <dict> <key>keychain-access-groups</key> <array> <string>XXXXXXX.*</string> </array>

Certificates and profile organization for multiple products

孤人 提交于 2020-01-13 02:09:27
问题 At my workplace we have completed development on one iOS app and are about to embark upon a second. Before doing so I wanted to clarify a few things regarding certificates and profiles and build environments: Q1: Am I correct in thinking that an Apple account can only have one distribution certificate, and that therefore this will be used in both apps? (via it being present in the provisioning profiles, I'll be creating a new set of profiles containing a new app id for the new app). Q2: As it

Xcode 9: Provisioning profile is Xcode managed, but signing settings require a manually managed profile

淺唱寂寞╮ 提交于 2020-01-10 08:08:08
问题 I need to archive my app for submission to iTunes Connect. It was OK with Xcode 8.3.3: It's NOT OK with Xcode 9.0: When archiving, I get: Code Signing Error: Provisioning profile "XC iOS: *" is Xcode managed, but signing settings require a manually managed profile. Code Signing Error: Code signing is required for product type 'Application' in SDK 'iOS 11.0' The two screenshots are taken from the same computer, same workspace. I can't use "Automatic" because it would change the provisioning

Does renewing a provisioning profile affect keychain access when I submit an app update to the AppStore?

喜夏-厌秋 提交于 2020-01-09 09:35:12
问题 I have an iPhone app that uses the keychain for authentication-related storage. I also had an expiring Provisioning Profile. In the documentation for keychain access it states: On iPhone, Keychain rights depend on the provisioning profile used to sign your application. Be sure to consistently use the same provisioning profile across different versions of your application. Because my Provisioning Profile was expiring, I renewed it (in the provisioning portal), downloaded it, and double-clicked

AppStore Submission Issue

匆匆过客 提交于 2020-01-06 18:10:06
问题 I am submitting my first iOS app to the app store and I am having an issue that I do not know how to resolve. Here is a recap of what I have done: I went to the iOS dev center, created a provisioning and distribution profile (for the app store), and uploaded them to Xcode. Then I went onto iTunes connect and completed the entire application. In itunes Connect, the app status reads as 'ready for upload'. So I go back into Xcode, and do an archive using the profiles I made for this project. I