provisioning-profile

Difference between development and distribution certificate [duplicate]

我与影子孤独终老i 提交于 2019-12-01 14:15:18
问题 This question already has answers here : Closed 8 years ago . Possible Duplicate: iPhone development - what is the difference between a development and distribution provisioning? What is the difference between development and distribution tab under certificate in iOS Provision Portal? Which one should be used and when? Is there any apple's strict criteria to choose them? 回答1: You use developer certificate for when you want to install the applications using XCode - mostly when developing.

Error Your account already has a valid iOS Distribution certificate

一笑奈何 提交于 2019-12-01 13:43:21
I've seen other questions with this kind of error, but none helped me to solve my problem. I have my personal apple developer account and one from the company I'm working for. When I'm trying to submit an app for my company in order to beta test it I have an error: "Your account already has a valid iOS Distribution certificate". I tried importing developer profile again, but it didn't helped. Just for documentation purposes: You need to edit your iOS Provisioning Profile in member center and select the correct Certificate delete your own apple id is from Xcode "preferences->Account-> Apple IDs

Error Your account already has a valid iOS Distribution certificate

徘徊边缘 提交于 2019-12-01 12:01:54
问题 I've seen other questions with this kind of error, but none helped me to solve my problem. I have my personal apple developer account and one from the company I'm working for. When I'm trying to submit an app for my company in order to beta test it I have an error: "Your account already has a valid iOS Distribution certificate". I tried importing developer profile again, but it didn't helped. 回答1: Just for documentation purposes: You need to edit your iOS Provisioning Profile in member center

Xcode 7.2: Failed to Locate or generated signing assets, Wild Card App IDs can not be used to create In House Provisioning Profiles

大兔子大兔子 提交于 2019-12-01 11:26:09
I signed an iOS App and WatchKit App & Extension targets with valid provisioning profiles (Separate provisioning profile for each app identifier, and not wild card App ID), Build was archived successfully but when I try to export/save Enterprise build, Xcode auto generate/locate XC: provisioning profile and it also and resets/invalidates previously selected provisioning profiles. I get below error. (even though we are not using Wild Card App IDs) "Failed to Locate or generated signing assets, Wild Card App IDs can not be used to create In House Provisioning Profiles". It seems like it is bug

WatchKit Upload

久未见 提交于 2019-12-01 10:51:38
I am trying to submit my WatchKit app t iTunesConnect. I click "Archive" and then validate and I am shown the message below. I have created an App Id for the app, extension and WatchKit App as well as distribution profiles. Where am I going wrong? Thanks To properly sign a watch app, you need three different App IDs and each App ID needs a provision profile. Go to Developer Member Center Add/Edit the three App IDs: One for your main App bundle, you may need to add the entitlements you need, like App Groups , Keychain Access Group . One for your watchkit extension bundle, you may need to add

iOS- Provisioning profile issues.

旧城冷巷雨未停 提交于 2019-12-01 10:28:15
问题 OK, so I have tried everything possible but still having issues. I am testing on two devices. An iPhone and an iPad. When I connect the iPhone to Xcode and hit run it builds on the iPhone without any problems but when I connect the iPad to Xcode and hit run it fails and gives me this This product type must be built using a provisioning profile, however no provisioning profile matching both the identity I used to be able to test very easily before I upgraded to Xcode5. Now it works on one

WatchKit Upload

僤鯓⒐⒋嵵緔 提交于 2019-12-01 07:34:24
问题 I am trying to submit my WatchKit app t iTunesConnect. I click "Archive" and then validate and I am shown the message below. I have created an App Id for the app, extension and WatchKit App as well as distribution profiles. Where am I going wrong? Thanks 回答1: To properly sign a watch app, you need three different App IDs and each App ID needs a provision profile. Go to Developer Member Center Add/Edit the three App IDs: One for your main App bundle, you may need to add the entitlements you

xcodebuild how to sign app with command line?

久未见 提交于 2019-12-01 06:02:25
I am trying to export an ipa using the command line, I can't do that within Xcode because the app is made for a client and I am not a member of his team (I really hope Apple changes that and makes it work like in Xcode 5 :/ ) Anyway, I did more research and tried this command: xcodebuild -exportArchive -archivePath pcdev.xcarchive -exportPath ~/Desktop/playcadeAdHoc.ipa -exportFormat ipa -PROVISIONING_PROFILE= xxxxxxx-8a61-4264-8fe9-0513bd7935e6 -CODE_SIGN_IDENTITY=iPhone Developer:xxxxx It did export the .ipa but I wasn't able to run it on my phone; I was stuck in the installing state. I went

Renew iOS Provisioning Profile on in-house app

对着背影说爱祢 提交于 2019-12-01 04:20:14
问题 My iOS Provisioning Profile will expire soon and I need to know the smoothest way to renew that profile. My certificate doesn't expire for another couple of years, so the certificate itself should be fine.It is an in-house (non-App Store) app and is installed on a number of devices. Which is why I'm wondering if the app will stop working if I do the following: Let the provisioning profile expire. Click generate inside the existing profile. If so, is there any way to update/renew the profile

creating ipa for distribution to client

心不动则不痛 提交于 2019-12-01 04:06:26
问题 I wanted to know what is the use to create an ipa and distribute it to client for testing when we can easily zip the built app and distribute the zipped .app file. What is the benefit of creating the .ipa ? Is it that creating the ipa do not need the mobile provisioning profile? Please clarify my doubt. 回答1: The ipa file is in fact the installable. I'd recommend reading the iOS Development Guide (see the "Distributing Applications" section in particular), as this explains everything in detail